On Tue, 2009-01-27 at 19:33 +0100, Lukáš Tinkl wrote:
> Dne Tuesday 27. of January 2009 19:26:13 Linuxguy123 napsal(a):
> > On Tue, 2009-01-27 at 17:06 +0000, José Matos wrote:
> > > On Tuesday 27 January 2009 16:52:28 Linuxguy123 wrote:
> > > > I knew that... I was hoping someone had an inside scoop or reason
why
> > > > its the way it is.
> > >
> > > Several of us have (probably) some ideas why that has happened, on the
> > > other hand your preamble will turn us way from giving any kind of answer.
> > >
> > > For example what do you understand as a real browser? Do (e)links, lynx
> > > or dillo (among others) qualify? If the they don't qualify why are
there
> > > users using them to browse the net?
> > >
> > > If you define a real browser as browser that deals with all the pages,
> > > then I am sorry but there aren't any. No single browser deals with
all
> > > pages (imagine those IE-only pages, as an example) so there are no real
> > > browsers. QED.
> >
> > When will Konqueror work as well as Firefox does as far as handling
> > webpages without errors ?
>
> I think José explained quite well your twisted perception of how the
"real"
> browser should look like. I for one know of many webpages that work correctly
> in Konqueror but fail miserably in Firefox; guess why? Because these pages
> were designed for IE only
OK, well here is an example page that Konqueror does not handle
properly:
http://www.linuxtoday.com/news_story.php3?ltsn=2009-01-27-015-35-IN-KE
I assume that Linux Today wouldn't write web pages that are "IE only".
The problem my konqueror has with this page is that it displays what
looks like a title bar incorrectly in the middle of the page. "Events
Blogs, Jobs, Partners...Search"
And the "Complete Story" link doesn't work.
So... I right click-> Open As... open it in Firefox and read the
story.
If you don't believe me, I'd be happy to send a screen shot.
I have been working with a khtml developer the past hour or so on this one.
Turns out there is one extra "</li>" in the html on that page where there
shouldn't be.
So the html is a bit messy. However, the developer says he can fix khtml
to be smarter about this.
In summary, we have a good chance for this bug to be fixed in 4.2.1