PageBlaster vs W3C CSS validation

Rate this topic:

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Author

Messages

DavidWSnow
<250Posts

Posts:213

06/14/2008 6:40 PM
I was doing a routine check of my site www.AgingSafely.com and clicked on Firefox Web Developer's Tools -> Validate CSS and the result was "Servlet has thrown exception:javax.servlet.ServletException: Timed out." I assumed that the W3C site was messed up and moved on. Afew days later I tried again. Then I checked a few other sites and it could validate them so I started to investigate. High on my list of suspects was PageBlaster since you really mess aground with the CSS. I went to my Home Page and disabled merging of CSS and JavaScript for .* After that I had NO ACCESS to my home page! I edied out PageBlaster and the site worked ok and the W3C CSS validation passed. I undid the exclutions for CSS and Javascript and I was back to the site working and W3C timing out. Any idea why seting the exclude path to exclude .* from CSSmerge & JS merge would trash my site? Any idea how to pass CSS validation and use PageBlaster at the same time? /DaveS

tabletennisstore
<50 Posts

Posts:35

06/14/2008 7:44 PM
I ran across few situations when my site http://www.TableTennisStore.us simply blanked out. I also have seen many weird css problems on Firefox. I'm a Internet Explorer fan, so I had not tested my site on Firefox until few days back when I heard Firebox is the popular browser. When it comes to caching, I have seen the problems everywhere in many applications. But the benefit caching can bring to the performance is awesome. I think Dave will help you with this. My site performance has improved and Dave is a nice guy who will look into the issues fast.

John Mitchell
Posts:3471

06/14/2008 11:16 PM
The pattern of each exclude item is used as the key so you can't have the same pattern on two different exclude paths. Use: < path pattern=".*" excludeFrom="MergeCSSAndJS" I don't know why PageBlaster would cause CSS not to validate unless it is because of the Minification. What validation errors are you getting.

DavidWSnow
<250Posts

Posts:213

06/15/2008 10:05 AM
The W3C error for the home page www.agingsafely.com is "Servlet has thrown exception:javax.servlet.ServletException: Timed out" when nothing is excluded. When I exclude ".*" excludeFrom="MergeCSSAndJS" ir now passes the W3C tests. Yesterday I couldn't even bring up the page. Go figure I left PB enabled so that you could look at the Minified CSS if you wanted. /DaveS

John Mitchell
Posts:3471

06/15/2008 10:16 AM
Sounds like a bug in their validation code since browsers can use the optimized version. I think it would be more important to have it optimized then to leave it unoptimized just so it passes their validation. You can try just removing the minification which still gives you 90% of the optimization since it does compression. pattern=".*" excludeFrom="CSSMin" You could also try just excluding specific css files if you want to see if it is only one.

DavidWSnow
<250Posts

Posts:213

06/15/2008 10:40 AM
Fails the same with excluding CSSMin /Dave

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.