T
Thomas 'PointedEars' Lahn
Garrett said:Thomas said:Not Valid.Garrett said:Garrett Smith wrote:
kangax wrote:
Thomas 'PointedEars' Lahn wrote:
[...]
Example
That was the wrong example, try again:-
<!doctype html>
True, but does trigger standards mode in the browsers tested (and that
has been discussed here).
Red herring.
Is that scorn or are you trying to discuss the use of |in| in host object?
I am just fascinated that although it has been discussed to death you still
use it.
Regarding the use of |in| with host object, I mentioned the "false
positive" edge case using "99999" in document.styleSheets in IE, nearly
1 month ago. I have been looking for more cases that fail. Such failure
cases would give more weight to the argument of |in| being inappropriate
for host objects.
Proof by (bad) example. The probability that there are 100'000 stylesheets
in a single document and that this needs to be tested is close to 0.
Given that we are talking host objects, `rules' may store any value at thisif(typeof rules != "undefined") {
point. The test is insufficient.
Smart people use "<\/" to hide ETAGO delimiters from SGML(-ish) parsersdocument.write("<pre>rules[0].selectorText: " + rules[0].selectorText
+ "<" + "/pre>");
since about the turn of the century.
It is a little easier to do it with a backslash.
It is also more efficient, easier legible, and easier to maintain.
Certainly much easier than arguing about it.
I don't know exactly what kind of fallacy this is, but it is one.
Either way would work, though.
Red herring.
Nobody tried (or would even attempt trying) to modify `selectorText' butdocument.write("<p>assign rules[0].selectorText = 'body'...</p>");
try {
rules[0].selectorText = "body";
you. You were willing to concede that point in
<yet one hour 22 minutes
later you are starting this again. What the heck is wrong with you?
I have noticed you have a tendency to blame others for not understanding
what you do not understand.
Ad hominem fallacy.
In this case, you seem to not understand is why I am testing assigning
to selectorText. The reason I am doing that is because I am curious as
to how browsers would handle that.
It is a waste of time trying to do things that are not supposed to work.
PointedEars