Hehe, glad to hear your code is clean Pat ;o) Well, if the W3C Markup Validation Service gives the html file a clean bill of health, it does look like the Quicklook shipping in OSX 10.10.2 is the problem.
Update: I¹ve just seen your latest email so the combo update didn¹t fix it. My gut feeling is that it is unlikely to be the particular computer model and that it still could be a page specific problem but my gut is often wrong ;o) - your file passes the W3C Markup Validation Service but maybe there is some (valid) code that quicklook can¹t handle. You could always test that by trying your page file on a computer that is known to display html in Quicklook (maybe email to Peter?) You could easily check if you have a Quicklook problem on ALL html files by just writing the most basic html page just valid html framework with, say, just one line of plain text content ³html test page². That might just confirm if the problem is with html files in general or just certain html content. Again, just a thought. Good luck Neil -- Neil R. Houghton Albany, Western Australia Tel: +61 8 9841 6063 Email: [email protected] on 4/2/15 12:10, [email protected] at [email protected] wrote: > Hi, again, Neil, > > Nothing dirty about my code. With BBEdit hanging over my shoulder with every > keystroke, there¹s little chance of that. I always verify the code on every > page just to catch the little oversights. > > Thanks, > Pat > >> On 4 Feb 2015, at 11:22, Neil Houghton <[email protected]> wrote: >> >> Re: OS 10.10.2 and Quicklook >> Hi Pat, >> >> Yes, I understand your point but, if it had worked, you wouldn¹t have had >> to CONTINUE to open in a browser first just a one-time thing for each file >> at least that¹s what I found with the PDFs the first opening of the file >> with the appropriate software seemed to generate the first ³preview² after >> that, Quicklook continued to work as it should (ie without having to first >> open the file). >> >> However, since this approach DIDN¹T work for you, the point is academic ;o) >> >> >> Good look with the combo update I guess if it is an OSX problem that could >> fix it. >> >> >> >> One other thought have you checked that your html is all valid modern >> browsers tend to handle dirty code quite gracefully but maybe the latest OSX >> Quicklook is less tolerant (this could perhaps explain why some people, like >> Peter, are finding Quicklook OK with html) again this is a bit of a long >> shot ;o) >> >> >> Whenever I create a webpage, I always run it through the W3C Markup >> Validation Service at <http://validator.w3.org/check> >>> This validator checks the markup validity of Web documents in HTML, XHTML, >>> SMIL, MathML, etc. If you wish to validate specific content such as RSS/Atom >>> feeds or CSS stylesheets, MobileOK content, or to find broken links, there >>> are other validators and tools available. As an alternative you can also try >>> our non-DTD-based validator. >> >> Just select the ³Validate by file upload² tab and you can browse to your html >> file, select it, and hit the ³check² button. >> If all your html is valid, it should come back with a ³passed² message >> otherwise it will highlight errors and warnings. >> >> I find this invaluable - it¹s amazing how many little errors sneak through >> and this makes it really easy to cleanup your code & get a pass mark ;o) >> >> Again, just a thought. >> >> >> >> Cheers >> >> >> >> Neil
-- The WA Macintosh User Group Mailing List -- Archives - <http://www.wamug.org.au/mailinglist/archives.shtml> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml> Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
