Re: Bed page display
In article 0ba4806653@abbeypress.net, Jim Nagel nets...@abbeypress.co.uk wrote: Tim Hill wrote on 29 Jun: ... save the web page to RAM disc and run it from there. As it can't find the 'faulty' CSS file from its relative URL, it is ignored. To see it more as intended you can use this link to load the 'invisible' css file http://www.cornishworkshop.co.uk/candyedit.css . Save it to ram disc alongside the web page as candyedit/css then edit it Hmm, is this a general technique that works with any site using CSS with tiresome features? The 'run it from ram disc' often does, yes. But if the page in question uses relative links to images c they will all be 'lost' unless you do a full save followed by deleting the css file(s) within the saved pseudo-app. It should then render even the relative stuff but in your browser default settings. Unfortunately, if they have done something unnecessary, such as using a fixed CSS path (as well) or setting the font color.. to white in the HTML and you have a default white background and they rely on a dark CSS set background, it could be tricky to read. ;-) Each page which mis-renders may have different badly written elements which need to be overcome! for stuff I simply want to read, 'save text' is sometimes the easiest, though I will often turn to my android tablet or PC, both of which have more capable browsers than NetSurf. I've often wondered how to see what the hidden CSS is doing. You can easily look at a page's HTML to determine the CSS file(s) it is using. By putting, e.g. http://sarva.co.uk/style.css in the address bar the CSS file is loaded. Although the page looks blank, pressing f8 in NetSurf should throw the content of the file into an editor. Fortunately CSS is almost human-readable but http://w3schools.com is there to explain anything not understood. F'rinstance my wee rant in the Sourceforge thread about text that is not only tiny but grey -- which I see too often on other sites, tho maybe it's my own eyesite! Does it look grey only because it is tiny and the anti-aliasing leaves hardly any black pixels? ;-) The whole page can be blown up in Netsurf using Zoom or a keypress I forget because I use my button bar instead. http://timil.com/riscos
Re: Bed page display
Tim Hill wrote on 29 Jun: ... save the web page to RAM disc and run it from there. As it can't find the 'faulty' CSS file from its relative URL, it is ignored. To see it more as intended you can use this link to load the 'invisible' css file http://www.cornishworkshop.co.uk/candyedit.css . Save it to ram disc alongside the web page as candyedit/css then edit it Hmm, is this a general technique that works with any site using CSS with tiresome features? I've often wondered how to see what the hidden CSS is doing. F'rinstance my wee rant in the Sourceforge thread about text that is not only tiny but grey -- which I see too often on other sites, tho maybe it's my own eyesite! -- Jim Nagelwww.archivemag.co.uk See you at Kenilworth? www.mug.riscos.org/show13 July 13
Re: Bed page display
Richard Torrens (lists) wrote on 28 Jun: http://www.cornishworkshop.co.uk/hammerhandle.html is a series of nested tgbles. The text overwrites, all on one line, with no proper wrapping in the cells. Couldn't find any beds (or tgbles!) on that workshop site! But then of course the overwritten text might explain this. ;=) -- Jim Nagelwww.archivemag.co.uk See you at Kenilworth? www.mug.riscos.org/show13 July 13
Bed page display
In article 5362eae127li...@torrens.org.uk, Richard Torrens (lists)
li...@torrens.org.uk wrote:
http://www.cornishworkshop.co.uk/hammerhandle.html
is a series of nested tgbles.
Yes, but not the problem, I think.
The text overwrites, all on one line, with no proper wrapping in the
cells.
I suspect this is because the page uses a CSS file which includes
body {line-height:0;...
A line-height of 0 is obviously undesirable and it is not reset to
override this for the other elements used on the page, AFAICS.
You can see it pretty much as intended if you save the web page to RAM
disc and run it from there. As it can't find the 'faulty' CSS file from
its relative URL, it is ignored.
To see it more as intended you can use this link to load the 'invisible'
css file http://www.cornishworkshop.co.uk/candyedit.css . Save it to ram
disc alongside the web page as candyedit/css then edit it and delete
line-height:0; in the first line. Save it. The page then displays
pretty much as intended. Luckily, the images use absolute references.
A good example of 'sledgehammer to crack nut' use of CSS as it adds
almost nothing worthwhile to the page content whatsoever.
Bed page display
http://www.cornishworkshop.co.uk/hammerhandle.html is a series of nested tgbles. The text overwrites, all on one line, with no proper wrapping in the cells. -- Richard Torrens. http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats and more!
