Re: safari rendering bug: site display not correct

In article <tph-E7E6FA.22301429122005@localhost>,
Tom Harrington <tph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> In article <41jp9pF1fdigqU1@xxxxxxxxxxxxxx>,
> Markus Dehmann <markus.dehmann@xxxxxxxxx> wrote:
>
> > I produced this little mini example that shows the problem:
> >
> > <html><body>
> > <div><p>plain<b>bold</p></div>
> > <div><p></b>plain</p></div>
> > </body></html>
> >
> > The second "plain" is not plain in safari, but it is in firefox and opera.

I produced a much more elaborate test page, showing the same problem
(you will note that I am not actually calling it a bug) with several
varieties of inline elements.

> The problem there is not Safari, it's your HTML. Your tags are not
> nested properly, so your HTML is not valid. Most browsers try to be
> flexible in what they accept, but here the error is clearly your own,
> and you cannot reasonably expect a specific rendering.

Tom, I'm not sure how much use it is to point out (totally correctly as
far as I am concerned) that the problem is invalid HTML. Yes, it would
probably be better for Markus if the comment entry form checked for
invalid elements and failure to close inline elements (and either
rejected or fixed them). But equally, it probably isn't anything that
Markus actually controls. Given the vast majority of web page creation
tools don't produce valid (X)HTML, it follows that the great majority of
web pages are also invalid. Interesting data point - last check I know
of, in 2002, only 6% of W3C members had valid front pages! If not them,
then who?

Markus asked about sending in a bug report. In Safari, second item in
the Safari menu is Report Bugs to Apple. If you know someone who has an
Apple Developer membership, see if they can also get it into one of the
more official problem lists. Checking Dave Hyatt's blog about Safari
might also be worthwhile. I can't recall if he had a comment section.

Personally I think an inline tag should be closed off when it hit
another block element. But that will break many badly written web
pages. Little wonder web developers like Dave Hyatt now seem to be
putting more of their attention on getting standard mode working better,
and ignoring problems with quirks mode rendering. I can't see anyone
being able to track all the problems there.

Mind you, I also think pages served as text/plain should be rendered as
text, and not rendered as HTML (even if that is the way IE does it).

--
http://www.ericlindsay.com
.

Relevant Pages

  • Re: trying to achieve Level Triple-A conformance
    ... rendering but also behaviour. ... that the HTML DTD requires. ... the way browsers occasionally do decide to repair it for you. ... Validation is the process of comparing a document that DTD. ...
    (alt.html)
  • Re: How can I prevent spaces between tags being rendered?
    ... By not embedding whitespace (spaces or linebreaks, ... Whatever the rules for rendering HTML & CSS say, ... Remember that you can place whitespace _inside_ tags quite easily, ...
    (comp.infosystems.www.authoring.stylesheets)
  • Re: for those that think jpgs are "safe"
    ... HTML, and simply use Javascript instead of VBScript, then it would ... >> really HTML will render the page as HTML in Internet Explorer, ... >> but this in itself is not a security vulnerability. ... Internet Explorer rendering what's named as an JPEG as something ...
    (alt.computer.security)
  • Re: Html Rendering in Winforms
    ... I am facing a problem with the rendering of html into a windows ... control so far. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: The technique to capture HTML into JPG file
    ... method to capture the HTML into JPG file, given the start and end x,y ... rectangular area into JPG file. ... Or maybe I can use an invisible window to let browser render ... You definitely would need something that does the rendering, ...
    (comp.unix.programmer)