Pages 1 2 and Next are shown in separate lines
-
wrote on 10 May 2010, 06:09 last edited by
On the forum the links to pages 1 2 and Next are shown in separate lines (checked on Chrome). They should have been on a single line.
-
wrote on 10 May 2010, 07:20 last edited by
Thanks for reporting this. We're aware of this as its a known issue in Chrome. We'll hopefully have a fix during the day.
-
wrote on 10 May 2010, 07:20 last edited by
Firefox and IE works fine though.
-
wrote on 10 May 2010, 07:27 last edited by
[quote author="JohnDoe" date="1273476036"]Firefox and IE works fine though.[/quote]
Yes me too checked it on Firefox, its working fine.
Anyone having Opera Browser?
-
wrote on 10 May 2010, 07:33 last edited by
Its a Chrome-thing so it should work fine in Opera as well.
-
wrote on 10 May 2010, 07:34 last edited by
I reported it on the bug tracker: http://bugreports.qt.nokia.com/browse/QTWEBSITE-22
-
wrote on 10 May 2010, 08:06 last edited by
IE6 has still around 8% market share. Will developer network be backward compatible with IE6?
-
wrote on 10 May 2010, 08:24 last edited by
bq. IE6 has still around 8% market share. Will developer network be backward compatible with IE6?
I hope not :)
Even if global market share is ~8%, I hope the IE market share among developers is closer to 0% :) -
wrote on 10 May 2010, 08:37 last edited by
On this site we don't plan to fully support IE6, unlike on qt.nokia.com, Qt web shop and others where we do. In fact, if you arrive at this site with IE6 a banner notice on top of the screen will be shown saying that the site might not work as intended for your browser.
When things have calmed down on development of this site I plan to improve the support for IE6 - so it's not "broken" at least.
-
wrote on 10 May 2010, 10:13 last edited by
Actually, that seems to be a WebKit issue. Safari breaks the lines too.
-
wrote on 10 May 2010, 11:06 last edited by
[quote author="Alexandra Leisse" date="1273486422"]Actually, that seems to be a WebKit issue. Safari breaks the lines too.[/quote]
I would hardly say it is a WebKit issue. It looks like broken HTML to me, the parser is probably trying to make sense out of the <td> tag.
I will have a look if it is worth modifying WebKit. -
wrote on 10 May 2010, 11:29 last edited by
Let me rephrase: it seems to be an issue on WebKit based browsers. It's on our lists of bugs.
-
wrote on 10 May 2010, 14:43 last edited by
We have a fix for it, it will not make today's deployment but maybe tomorrow.
-
wrote on 11 May 2010, 06:51 last edited by
Just checked it seems it has been fixed now
1/14