|
|
Posted by dorayme on 02/17/07 00:47
In article <16dct2hat56aj1ses021gcdpbnc68s0d81@4ax.com>,
Andy Dingley <dingbat@codesmiths.com> wrote:
> On Sat, 17 Feb 2007 08:53:41 +1100, dorayme
> <doraymeRidThis@optusnet.com.au> wrote:
>
> >Suppose you want to know if a #navMonday css instruction can be
> >safely removed from your CSS sheets. All you have to do is search
> >for ' id="navMonday" ' over the folder that contains all the
> >website files.
>
> That's OK for one class or id, but how about the ful llist?
>
Yes, see my reply to Ben. The special case of a need to check
every id and class is far fetched but interesting. I leave you
with that one. What would I know off such things? But
realistically, think about it, you will straight off be able to
see many ids and classes and things that are not worth searching
for by simple inspection of a few pages of the html, they are
clearly used. Earthlings are fast and good at knowing after brief
inspections what is not worth bothering about.
> With an editor, how do you produce the full list? You'd need an editor
> and regex to match everything that _wasn't_ an id and then strip it.
> That gets tricky.
Am I missing something big here? I thought it was about something
in a css sheet that was uselessly there because nowhere is it
used in the html. So if it is not there in the html, nothing
needs to be done to the html. As for the css, well, these are
just not going to be thousands of pages, not on earth at least,
it does not happen. And there will not be that many of them. And
if some are missed in what I am proposing, they will do no harm
and will be picked up in later sweeps.
I am not trying to spoil a party here, just trying to inject a
bit of common sense into it.
--
dorayme
Navigation:
[Reply to this message]
|