Istvan Gabor wrote:
That's what I did too. What I don't understand is this: The browser has the html code to show the content on screen. Why is the browser not able to save this code as html file? The is very little HTML on that page. Almost all of it is javascript.
The content you see is fetched from a database and displayed in a <iframe> using a separate "div" for each line in a container that is height and width = *** 0 ***. So all of it is handled as "overflow" (which is set to hidden). As you scroll down, it transfers content into the *empty template* that is the page you see. So when you save, all you get is the template code. And printing -- never quite understood why the print-to-file function didn't paginate. Maybe because the size is 0 it thinks it has everything on the 1st page. The print bit I've seen on other sites. Each frickin line is in it's own container... how awful. They know exactly what line you left off reading. Their interface also violates a basic HTML/website design principle -- that of being able to progressively degrade in the presence of less powerful browsers... If you try to read it with a browser like "lynx" (text only)... you are told to enable javascript (which you can't)...The interface completely fails if you don't have javascript. Nasty stuff. Maybe there's a FF extension at addons.mozilla.org that might help, but the template itself looks like it was generated by a template... which makes for human reading: difficult. Good reason NOT to use google as your group interface. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org