Hi all. I find that nothing happens when I click links on side bar within google news. On this page (http://news.google.com/news?ned=us), there are links such as World, U.S. and so on. None of them is clickable. Regards, furaisanjin
Hi, On Wed, Feb 11, 2009 at 05:40:15PM +0900, furaisanjin wrote:
Hi all.
I find that nothing happens when I click links on side bar within google news.
On this page (http://news.google.com/news?ned=us), there are links such as World, U.S. and so on. None of them is clickable.
That's because they use some javascript to handle these buttons. However the cursor changes because of CSS. If you switch off CSS or use dillo-2.0, the cursor will not change. That makes me think whether it is a good idea to let the cursor be changed from CSS. For example: <a href="dangerous" style="cursor:default">harmless</a> might trick someone to click a link it doesn't want to. Or am I paranoid here? Regards, Johannes
I notice that dillo doesn't allow <div> inside <a>. That's why link doesn't work. This is one example from news.google.com. <a class=d href="/news?ned=us&topic=w"> <div class=naventry> <font size=-1> <b> World</b> </font> </div> </a> Regards, furaisanjin
On Wed, Feb 11, 2009 at 08:40:01PM +0900, furaisanjin wrote:
I notice that dillo doesn't allow <div> inside <a>. That's why link doesn't work. This is one example from news.google.com.
<a class=d href="/news?ned=us&topic=w"> <div class=naventry> <font size=-1> <b> World</b> </font> </div> </a>
Yes. It's dillo trying to follow and help others to play by standards. This page has more than a hundred bugs in the bug-meter. A is an "inline container", DIV is a "block element". Only "block containers" are allowed to have "block elements" inside. Hence it is a bug. In this case Dillo closes the inline container and keeps on parsing. BTW, this is the same reason why you can't make a link out of a TABLE. -- Cheers Jorge.-
On Wed, Feb 11, 2009 at 09:37:59AM -0300, Jorge Arellano Cid wrote:
A is an "inline container", DIV is a "block element". Only "block containers" are allowed to have "block elements" inside. Hence it is a bug. In this case Dillo closes the inline container and keeps on parsing.
Could the Dillo parser emit the warning but not close the container? The result would be more useful to the user, and web devs who care about correctness would still see the warning. (Disclaimer: I have no idea whether my suggestion is feasible, it's just a thought.) Regards, Jeremy Henty
Johannes wrote:
That makes me think whether it is a good idea to let the cursor be changed from CSS. For example:
<a href="dangerous" style="cursor:default">harmless</a>
might trick someone to click a link it doesn't want to. Or am I paranoid here?
If it's paranoia, it's a healthy paranoia :) (I already had to force underlining of links in style.css. I can't understand why non-malicious sites turn that off to make it hard to tell what's what.)
participants (5)
-
corvid＠lavabit.com -
furaisanjin＠gmail.com -
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de -
onepoint＠starurchin.org