Jude DaShiell wrote: > I changed the user-agent to w3m and encoding to none and did log into > m.facebook.com but the page is a mess links inaccurately labeled and > search for groups so far as I can tell doesn't appear on that page.
Jude, Hit control-V to turn on "tag soup" alternative HTML parsing. You could also use the 'l' (letter ell) command to view what Lynx sees as hidden links -- but the result will be truly awful... ======================================================================== Despite the horrible mess of code that Facebook sends, this does look like it's probably a Lynx bug. I boiled the problematic document down to this: <a href="foo"><div>Link hidden due to div encapsulation?</div></a> -- and Lynx displays it as an active link only in TagSoup parsing mode. The seemingly equivalent documents: <a href="foo"><span>Link hidden due to span encapsulation?</span></a> <a href="foo"><zort>Link hidden due to zort encapsulation?</zort></a> do not behave that way. Well, perhaps not a Lynx bug. <span> is an inline element while <div> is block-level, and not allowed inside <a>. (And apparently mystery tags are considered "inline".) So the code being fed to Lynx is wrong. Yet the result seems overly punitive to the user... http://stackoverflow.com/questions/1827965 seems to cover this well. http://html5doctor.com/block-level-links-in-html-5 says it's legal in HTML5, FWIW. >Bela< _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
