|
Posted by Hairy One Kenobi on August 13, 2005, 8:32 am
If you were Registered and logged in, you could reply and use other advanced thread options
> >
> > Usual HTML development procedure: decide what to write (often an hour or
> > two), format it for use in IE (a couple of minutes, on my home-grown
content
> > management system), then try and work our which bits of Firefox don't
work,
> > or have stopped working, and try and find workarounds (open ended, often
> > days)
>
> Of course, the opposite would hold equally true.
Granted. The problem is when something that has worked for ynks gets..
"unfixed".
Can't remember the exact details ('twas a while ago), but I think that it
involved containers within containers. IIRC, Nutscrape had a hard-coded
limit of four DIVs/SPANs/whatevers, Firefox fixed it, and then broke it in
the next release...
>
> > Not that I'm criticising it as an alternative browser, just that it's
far
> > from complete in supporting standards. Both browsers have some pretty
horrid
> > limitations.
>
> This is true, although firefox is much closer to standards conformance
than
> IE. More to the point, firefox developers consider not complying with an
> official standard to be a bug, and something that should be fixed
(eventually).
> MS does not take this view with IE, and that anti-standards attitude is a
> good reason for a boycot.
Well, they need to take a look at text-align:center. Been broke for as long
as I've been using it. Come to think of it, I've had to use a lot of SPANs
when I /really/ should have been using DIVs. Works in IE, but not in
Firefox. My guess would be that IE got kludged to match Mozilla behaviour,
in addition to the standards.
http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4 gives a good
overview on how you really shouldn't be using SPANs as block elements... but
FF CSS limitations mandate it.
As I said, *both* browsers have some pretty horrid limitations.
H1K
| 
XML site map