A proper way to put code before </head> tag

[OZO]

(Dec. 12, 2010 09:11 PM)JJoe Wrote:  "Exceptions.ptxt" should belong to the publisher of the set as 'unofficial' modifications to it ( and some other files ) may make it difficult to help users.

I agree with you. And this thread - Google Light Theme - fixed 2010-05-06 - is a good example of such problem. I always thought that other users use the same set of filters as I do and assumed that if the filter was working for me - it was working for everybody. Which, as we see now, was not the case The only way to have a control over a new custom filter is to keep some base environment (e.g. 2010-10-23) and keep track on what specifically should be changed in that set in order to make the new custom filter working. And that's exactly what I'm, going to do with that thread next.

Quote:So, for now, I think it is best for us to use "Exceptions-U.ptxt" and or filters to add routines. I'd guess that most people would rather import filters than edit "Exceptions-U.ptxt". It should be easy enough to add these things to an official set if necessary.

If I get your point correctly, from the perspective of an easy way to add new filters in future official sets (if necessary) the best way to do it now (and in this particular case, to make this IE6 exception) is to use "Exceptions-U.ptxt" rather then to put corresponding filter into "default.cfg". Right?

Quote:Also wondering why, display or security, Google is sending this code to IE6.

I don't have an answer to this question. And as I've mentioned earlier, additionally to the different layout (TABLEs instead of DIVs), IE6 version doesn't have <noscript> code. Other versions of IE get this code. Do Google developers assume that IE6 users always use JavaScript? Or they just want to "punish" them if they don't? It looks strange...