Re: [kde-linux] Cannot access certain site

On Wednesday 02 April 2008 13:45, david wrote:
Agreed.  Using your technique I confirm that konqueror has the same
problem on this system too.  However, firefox does not.

Better - or different - error handling would be my guess. Handling HTML
tag soup has been a problem for browser developers for a long time now.
I'm not familiar with how much the W3C standards have to say about error
handling beyond the standard guideline of "If you don't recognize it,
ignore it" (applied to tags / attributes / values). When faced with
items like missing closing tags, the browser basically has to "guess"
where the page author wanted to put the missing tag. How a browser
figures that out varies from browser to browser. IE is notorious for
accepting almost anything, partly because it's willing to take more
radical guesses (based on its programmers ideas of what users expect
pages to look like). Netscape / Mozilla were more likely to stick with
standards and simply reject the mess if they couldn't make sense of
them. I don't know where Konqueror falls on that spectrum.

Sadly, too many sites are only checked against IE. Nothing much we can do
about that, apart from complain to the site owners.

Anne
___________________________________________________
This message is from the kde-linux mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Relevant Pages

  • Re: [kde-linux] Cannot access certain site
    ... Better - or different - error handling would be my guess. ... Handling HTML tag soup has been a problem for browser developers ... Firefox & Konqueror" It seems that Konqueror ...
    (KDE)
  • Re: [kde-linux] Cannot access certain site
    ... Better - or different - error handling would be my guess. ... tag soup has been a problem for browser developers for a long time now. ... I'm not familiar with how much the W3C standards have to say about error ...
    (KDE)
  • Re: OT: HTML (WAS: MF having issues?)
    ... Right, the example above, with the tag, comes from web developers inapporpriately depending on undocumented features. ... But let's say I don't actually read the standards, but just try out the tag to see what it does, and I notice that on my particular browser, the tag displays the text in italics. ... So now my HTML page may be broken, for example, if it contained text like this: ...
    (comp.lang.cobol)
  • Re: Refresh of photo upload page in Browser too quick
    ... Images are served separately from the main html file, based on the tag. ... Rather, I suspect you're building the code based on the old file and placing the old filename in it. ... And instead of fetching the image, the browser is looking in its cache and just using that image. ... Then, after a refresh, your code generates a new tag with the new filename, so the browser gets the updated image (or, in the case of a deleted image, the code generates no tag). ...
    (comp.lang.php)
  • Re: OT: HTML (WAS: MF having issues?)
    ... But let's say I don't actually read the standards, but just try out the tag to see what it does, and I notice that on my particular browser, the tag displays the text in italics. ... So now my HTML page may be broken, for example, if it contained text like this: ... The idea is that browsers who do not recognize the <applet> tag will simply ignore that tag, and display the text without any special formatting. ...
    (comp.lang.cobol)