Eric Pascarello wrote:Develop pages to work with JavaScript disabled?
Eric
Are you suggesting using a <noscript/>?
(1) - Say for a page I have 50+ 200kb images. Would this still be a good idea/practice to load all these images when JS is disabled?
(2) - I'll tell you all what I did. I simply extracted all my data into
![]()
elements and placed them in a TextArea so that the
![]()
is interpreted as text and not rendered as HTML(picture doesn't load then). I then did a display:none; on the parent container holding these
![]()
elements. This allows the content to be spidered; however, for human non-JS enabled broswers, users simply won't get any images and won't see the TextArea content....or I could just load a few pics in a <noscript/>. The latter part is what I'm leaning toward now....
The problem with the second way, the way I decided to do it (except the few pics by default), is that it doesn't appear my data within the TextArea is getting spidered. Does google ignore TextArea? I've seen many say no, but it's been a month and normally it only takes a week for my data to get into the indexes. Since this change, other content has made it in google indexes as well. Perhaps I'm being iimpatient? Perhaps google doesn't read TextArea? Perhaps it is somehow interpreting my CSS and seeing the parent container is set to deiplay:none? Perhaps #2 is a bad idea and I should be doing #1?