JD_Toims - 4:56 pm on Sep 3, 2013 (gmt 0)
1. It's best to avoid inline style attributes, as it makes maintenance more difficult, adds to your page weight that won't be cached, and prevents a clean separation of layers (content/presentation/behavior).
Always -- I just didn't edit what was there and kept with the same style of coding. [Sometimes I just plain don't have time to point out everything, but can give a "push" in the direction of working and let the poster sort out the details.]
2. I've found it's usually not a good idea to style the form element itself, but rather style some container element within the form. I don't remember the specifics, but I had some problems a few years back with browser inconsistencies (so it may not be an issue still). In any case, I try to avoid directly applying presentation to a form.
That's surprising on a form, but not totally shocking -- I ran into something similar when <section> and <aside> were first introduced though, so I'm a bit hesitant with applying a style to them still, even though they appear to be working fine now.
I understand. Interestingly, when I looked into it [years ago] I found it was recommended by someone working on the w3 docs, because of the ability for it to be better interpreted by screen readers at the time [or something along those lines].
[Of course I can't find the resource any more and the recommendation could have changed, because I don't bother looking into what works very often -- just don't have time lol -- but the reason I started using it was an explanation / recommendation by someone "in-the-know" at the w3.]