[opensuse] saving or printing google forum page
Hello: I would like to save and/or print google forum topic pages for future reference and offline use. For example this page: https://productforums.google.com/forum/?hl=en#!topic/gmail/Ajayw8WrwRQ If I save it in my browser using save page as in firefox or save as in opera, the resulted saved html file does not contain the page's content. I can not view the content offline. If I try to print the page to pdf file in firefox, only one page gets into the file and the comments from the lower part of the page are cut off. How could I save and or print the page so that I could view the content offline? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, July 22, 2014 06:04:03 PM Istvan Gabor wrote:
Hello:
I would like to save and/or print google forum topic pages for future reference and offline use. For example this page:
https://productforums.google.com/forum/?hl=en#!topic/gmail/Ajayw8WrwRQ
If I save it in my browser using save page as in firefox or save as in opera, the resulted saved html file does not contain the page's content. I can not view the content offline.
If I try to print the page to pdf file in firefox, only one page gets into the file and the comments from the lower part of the page are cut off.
How could I save and or print the page so that I could view the content offline?
Thanks,
Istvan
You are stuck in a catch 22, and perhaps its by Google's design. Even if you click the little down arrow within a circle just beyond the words "4 authors", and select "Expand all" it will not print anything that does not fit within the browser window. The Print task reloads the page into the browser window, but But I don't think it runs the javascript, and perhaps that is part of the problem. In any event, I've tried with all the linux browsers that I have installed and they all operate this way. So do the windows browsers I've tried. So I suspect that google went out of their way to cause this to prevent someone printing a zillion page thread. For reasonably small threads like the one you linked to you can outsmart this with the following work around: 1) Make sure you have selected Expand All as explained above 2) Grab the title bar of the Browser window, 3) Drag the window DOWN the screen such that it is mostly off screen. 4) Grab the top edge of the title bar, and start dragging upward (expanding the browser window). Keep an eye on the scroll bar. 5) When the scroll bar thumb (slider) disappears from the scroll bar, you have expanded the depth of the window sufficiently to contain the full thread, even though you can't see it because most of it is off the bottom of your screen. 6) NOW select print, and it will print the entire thread. This was done in KDE, so YMMV with other DEs which may handle window expansion slightly differently. --
From the Myth of Me -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/22/2014 02:20 PM, John M Andersen wrote:
On Tuesday, July 22, 2014 06:04:03 PM Istvan Gabor wrote:
Hello:
I would like to save and/or print google forum topic pages for future reference and offline use. For example this page:
https://productforums.google.com/forum/?hl=en#!topic/gmail/Ajayw8WrwRQ
If I save it in my browser using save page as in firefox or save as in opera, the resulted saved html file does not contain the page's content. I can not view the content offline.
If I try to print the page to pdf file in firefox, only one page gets into the file and the comments from the lower part of the page are cut off.
How could I save and or print the page so that I could view the content offline?
Thanks,
Istvan You are stuck in a catch 22, and perhaps its by Google's design.
Even if you click the little down arrow within a circle just beyond the words "4 authors", and select "Expand all" it will not print anything that does not fit within the browser window.
The Print task reloads the page into the browser window, but But I don't think it runs the javascript, and perhaps that is part of the problem.
In any event, I've tried with all the linux browsers that I have installed and they all operate this way. So do the windows browsers I've tried. So I suspect that google went out of their way to cause this to prevent someone printing a zillion page thread.
For reasonably small threads like the one you linked to you can outsmart this with the following work around:
1) Make sure you have selected Expand All as explained above 2) Grab the title bar of the Browser window, 3) Drag the window DOWN the screen such that it is mostly off screen. 4) Grab the top edge of the title bar, and start dragging upward (expanding the browser window). Keep an eye on the scroll bar. 5) When the scroll bar thumb (slider) disappears from the scroll bar, you have expanded the depth of the window sufficiently to contain the full thread, even though you can't see it because most of it is off the bottom of your screen. 6) NOW select print, and it will print the entire thread.
This was done in KDE, so YMMV with other DEs which may handle window expansion slightly differently.
It adds a couple steps but in Firefox I highlighted the thread and copy/pasted it into Kate. From there you can do whatever. -- Those who expect to reap the blessings of freedom must. like men, undergo the fatigue of supporting it.-Thomas Paine _ _... ..._ _ _._ ._ ..... ._.. ... .._ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Billie Walsh írta:
On 07/22/2014 02:20 PM, John M Andersen wrote:
On Tuesday, July 22, 2014 06:04:03 PM Istvan Gabor wrote:
[LONG SNIP]
It adds a couple steps but in Firefox I highlighted the thread and copy/pasted it into Kate. From there you can do whatever.
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? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/23/2014 09:02 AM, Istvan Gabor wrote:
Billie Walsh írta:
On 07/22/2014 02:20 PM, John M Andersen wrote:
On Tuesday, July 22, 2014 06:04:03 PM Istvan Gabor wrote:
[LONG SNIP]
It adds a couple steps but in Firefox I highlighted the thread and copy/pasted it into Kate. From there you can do whatever.
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?
If you look 'under the hood' at the raw html you will see that there is an astounding amount of javascript. I haven't decompiled it but it could well be that this is interfering with your print and save capability. You might want to ry installing one of the plug-ins for developers which will allow you to modify the DOM and even blank out the javascript. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 2014-07-22 21:20, John M Andersen wrote:
For reasonably small threads like the one you linked to you can outsmart this with the following work around:
I select what I want to print, then paste it into libreoffice, editing what I want out, saving paper. Or, you could try reducing font size ("ctrl -" in firefox). -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
John M Andersen írta:
On Tuesday, July 22, 2014 06:04:03 PM Istvan Gabor wrote:
Hello:
I would like to save and/or print google forum topic pages for future reference and offline use. For example this page:
https://productforums.google.com/forum/?hl=en#!topic/gmail/Ajayw8WrwRQ
If I save it in my browser using save page as in firefox or save as in opera, the resulted saved html file does not contain the page's content. I can not view the content offline.
If I try to print the page to pdf file in firefox, only one page gets into the file and the comments from the lower part of the page are cut off.
How could I save and or print the page so that I could view the content offline?
Thanks,
Istvan
You are stuck in a catch 22, and perhaps its by Google's design.
Even if you click the little down arrow within a circle just beyond the words "4 authors", and select "Expand all" it will not print anything that does not fit within the browser window.
The Print task reloads the page into the browser window, but But I don't think it runs the javascript, and perhaps that is part of the problem.
In any event, I've tried with all the linux browsers that I have installed and they all operate this way. So do the windows browsers I've tried. So I suspect that google went out of their way to cause this to prevent someone printing a zillion page thread.
Thanks. I don't see why it is good for google to prevent printing of a discussion. I think is is a shortcoming of the browsers they are unable to print/save something which is already on screen/cache. I thought there's some trick to force the browser to save the content as html. Would not be it as simple as only saving the very html code that codes for what is shown in the browser's window?
For reasonably small threads like the one you linked to you can outsmart this with the following work around:
1) Make sure you have selected Expand All as explained above 2) Grab the title bar of the Browser window, 3) Drag the window DOWN the screen such that it is mostly off screen. 4) Grab the top edge of the title bar, and start dragging upward (expanding the browser window). Keep an eye on the scroll bar. 5) When the scroll bar thumb (slider) disappears from the scroll bar, you have expanded the depth of the window sufficiently to contain the full thread, even though you can't see it because most of it is off the bottom of your screen. 6) NOW select print, and it will print the entire thread.
I selected everything and copy/pasted it into a text window. Seemed simpler. Thanks again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/23/2014 08:58 AM, Istvan Gabor wrote:
I think is is a shortcoming of the browsers they are unable to print/save something which is already on screen/cache.
Of course you might object if the browser failed to obey the javascript that was embedded in the page ... -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-23 15:29, Anton Aylward wrote:
On 07/23/2014 08:58 AM, Istvan Gabor wrote:
I think is is a shortcoming of the browsers they are unable to print/save something which is already on screen/cache.
Of course you might object if the browser failed to obey the javascript that was embedded in the page ...
And besides that, the html code used for printing is not the one used for display. This is intentional and controlled by the web page. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 07/23/2014 11:57 AM, Carlos E. R. wrote:
On 2014-07-23 15:29, Anton Aylward wrote:
On 07/23/2014 08:58 AM, Istvan Gabor wrote:
I think is is a shortcoming of the browsers they are unable to print/save something which is already on screen/cache.
Of course you might object if the browser failed to obey the javascript that was embedded in the page ...
And besides that, the html code used for printing is not the one used for display. This is intentional and controlled by the web page.
many sites, wikipedia is a good example, explicitly have different CSS for printing. Its easy to do. The same logic holds for displaying on phones and tablets. I don't know if such capability exists in HTML5 to control the html depending in the type of display. But then once you introduce JavaScript you can make anything happen, even to the point of only displaying on certain sized displays. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Jul 23, 2014 at 9:29 AM, Anton Aylward
On 07/23/2014 08:58 AM, Istvan Gabor wrote:
I think is is a shortcoming of the browsers they are unable to print/save something which is already on screen/cache.
Of course you might object if the browser failed to obey the javascript that was embedded in the page ...
Part of the problem, then, is that there are too few constraints on JavaScript programmers. They waste resources without cost to themselves. I usually have lots of pages open in FireFox (which we know is a resource hog to begin with), to the point that FF is consuming 4 GB of RAM; and then awaken in the morning that one or more of the pages that I'd left open has gobbled up another 3.5 GB of RAM, to the point that the system locks up and eventually crashes. They make certain pages behave in a manner that is counter-intuitive to most users, as is the case that began this thread. I have seen JavaScript malware that makes it exceedingly difficult to close the page containing it or that tries to force you to subscribe to something before letting you go. I say this as a developer. I find JavaScript to be a priceless tool for greatly enhancing the user's experience for the pages I work on; but I see peers doing things with that power that, in my lab, would be a firing offense. Alas, there are no easy answers. Every capability that I see JavaScript supporting, and that I have seen abused, also, in a different context, can be used to enhance user experience. But, we're at the merecy of browser developers and a subpopulation of developers that do bad things.
-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon?
Gotta love this. Cheers Ted -- R.E.(Ted) Byers, Ph.D.,Ed.D. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Anton Aylward -
Billie Walsh -
Carlos E. R. -
Istvan Gabor -
John M Andersen -
Linda Walsh -
Ted Byers