fuf posted:

omg Internet Explorer 8
So much wasted time.

Three things:

1) What is the actual market share for IE8? I keep seeing different numbers, ranging from like 1% to 20%.

fuf posted:

2) What are people's thoughts on displaying a "You are using an outdated browser, you should update" message for IE8 users? Do you think maybe it comes across badly and annoys users?

fuf posted:

3) Bootstrap etc advocate a "mobile first" approach where you default to a one-column mobile layout and then use media queries to adjust for wider screens. But IE8 doesn't support media queries. So do you a) write a whole separate stylesheet for IE8? b) use a polyfill to get media queries working in IE8, or c) forget "mobile first" and make your default layout the one that IE8 users will see?
(I couldn't get (b) to work, so I did (a). If I was starting from scratch I think I would do (c))

fuf posted:

omg Internet Explorer 8
So much wasted time.

Three things:

2) What are people's thoughts on displaying a "You are using an outdated browser, you should update" message for IE8 users?

Lumpy posted:

Remember that a non-trivial percentage if people using IE 8 simply cannot update or use anything else due to organizationa policy.

As for #3, if your site is usable even if you delete your media queries, who cares if IE8 gets the "mobile" version. That said, if your mobile container rule isn't width:100%;max-width:some-sane-number-based-on-your-type-size then you should switch frameworks or tweak yours so it is that way.

EAT THE EGGS RICOLA posted:

The only reason my firm updated away from IE8 is that our biggest/most important vendor put a "welp sorry dudes better upgrade" message up, and as a result we upgraded within a week after a VIP freaked out.

Thermopyle posted:

I'm looking for ideas/inspiration for a modern-looking way for adding a related object in a CRUD-style app.

For example, say I have a form for adding a Job to the users database. A Job can have associated Vendors and the form allows the user to select an existing Vendor or add a new one. What's a nice way of doing this?

My current dumb version has a section of the form that has a list of currently added vendors, a section for selecting an existing vendor, and a link that pops up a modal with a form for adding a new vendor.

Any other ideas, or can you point me to any sites doing this in an interesting way?

Thermopyle posted:

I'm looking for ideas/inspiration for a modern-looking way for adding a related object in a CRUD-style app.

For example, say I have a form for adding a Job to the users database. A Job can have associated Vendors and the form allows the user to select an existing Vendor or add a new one. What's a nice way of doing this?

My current dumb version has a section of the form that has a list of currently added vendors, a section for selecting an existing vendor, and a link that pops up a modal with a form for adding a new vendor.

Any other ideas, or can you point me to any sites doing this in an interesting way?

Kobayashi posted:

Are you talking about the UI?

EAT THE EGGS RICOLA posted:

This is default behavior for has_many/belongs_to/children relationships in Hobo, which is a superfast prototyping thing for Rails. I would not really recommend it for anything serious at all, but I've used it a bunch of times when I've tried to get a fully functional app up and running in a couple hours.

Oh My Science posted:

ps. I won my contract negotiation and the non-compete was removed.

kedo posted:

Contgrats! How'd you eventually get them to give in?

Thermopyle posted:

Yes.

RobertKerans posted:

I'm building something similar for my work at the minute, using basically the same visual pattern as a todo list. So you'd concatenate your separate lists + modal into one block (delineated by colour/horizontal separator/whatever), with the final list entry an 'add new' button. Expand/contract to display/enter further info, rather than pulling in a modal. Dead simple, basically stripping form styling and rebuilding with CSS/JS. I had some nice examples which I'll try and dig out.

kedo posted:

Contgrats! How'd you eventually get them to give in?

fuf posted:

omg Internet Explorer 8
So much wasted time.

Lumpy posted:

If you have a lot of entries, making 'add new' the last one in a list can make discovery of that option very hard. Make sure you test with 100 or 500 entries.

2banks1swap.avi posted:

Potentially dumb question I'm having a hard time googling for whatever reason:

What's an easy way to set something on a parent container and all child containers that tells the browser "render this when you try to print, but not anything above this in the DOM" ?

Subjunctive posted:

code:

<link rel="stylesheet" href="print.css" type="text/css" media="print" />

<div class="outer">
    Don't print me.
    <div class="inner">
    But do print me.
    </div>
</div>

code:

/* print.css */
.outer { visibility: collapse; }
.inner { visibility: visible; position: absolute; top: 0; left; 0 }

This will keep the rest from rendering, but it could cause a bunch of blank space to be allocated. To do otherwise, you could use "Print this!" button that hoisted out the relevant part of the DOM, hid the rest, and called window.print.

cbirdsong posted:

Couldn't you just do something like:

code:

.outer > * {
     display: none;
}
.outer > .inner {
     display: block;
}

Would break if .inner is nested in anything, but you could work around that.

Sulla-Marius 88 posted:

What exactly are you trying to do? I suppose you could add a css entry for everything NOT of the ID/class of the container and set display:none, but that's super hacky - :not doesn't really work well in IE I don't think.

You can't change the html layout and just throw everything prior to that in a container that then gets hidden..?

2banks1swap.avi posted:

Edit: To be less of a chode I'll actually answer.


Our project uses a top nav bar, left hand nav bar, and even a tab control bar. All the actually "stuff" anyone would ever want to print is inside of a content pane. I want to make that happen.

I want to let that content pane be printed/rendered when it's print time, but keep everything else from being rendered. Also, ideally, if the content pane is scrollable (there's stuff stretching vertically) then I'd like it to render as such and print multiple pages.

kedo posted:

Some email clients strip out the <head> entirely, so I'd imagine that's why they move it to the body.

Subjunctive posted:

Widely-compatible HTML email is a dark art. Recommend not messing with the ritual or its components.

kedo posted:

Heskie posted:

Stealing this for my portfolio, thanks!