2 ms·

That's a fair perspective, but I'm left wondering if it sounds good only because it's very nebulous and hypothetical. I wonder if it would sound as good if yo

by pohl 17y ago

That's a fair perspective, but I'm left wondering if it sounds good only because it's very nebulous and hypothetical. I wonder if it would sound as good if you were to be more concrete. In particular, would you mention (or, at least, loosely characterize by subsystem or specification) some of the bugs in IE that you would consider a higher priority? I'm asking because all of the following appear fundamental to me: DOM Traversal, DOM Range, DOM2 Core, DOM2 Events, DOM2 Views, DOM2 Style, CSS3 selectors, ECMAScript conformance & garbage collection, the behavior of HTML forms when manipulated by script, the HTTP 1.1 Protocol... I admit that there are 4 tests for SVG and 2 for SMIL that could be placed at a much lower priority, and if IE were sitting at 94/100 for missing those then I might agree with you. (Those were among the bucket 5 tests that arrived via the contest.)

boucher 17y ago
But you are also speaking in broad strokes. For example, "DOM Traversal" is something that IE can do. How critical are the specific features of DOM Traversal that the ACID 3 test is testing? I don't want to spend much time doing bug triage for IE, I'm just saying it's not hard to imagine that their priorities don't include bugs which were obscure only a year ago.
- pohl 17y ago
  The specificity does not derive from my post, but from the source of the tests that you are arguing against being fixed, viewable by all, and well documented. The traversal tests seem like very reasonable cases to me. For example: // test 1: NodeFilters and Exceptions // test 2: Removing nodes during iteration // test 4: ignoring whitespace text nodes with node iterators // test 5: ignoring whitespace text nodes with tree walkers I just wanted to know if you had something in mind or were just making vague apologies for the IE team. Either case is ok with me.

by pohl 17y ago

boucher 17y ago

But you are also speaking in broad strokes. For example, "DOM Traversal" is something that IE can do. How critical are the specific features of DOM Traversal that the ACID 3 test is testing? I don't want to spend much time doing bug triage for IE, I'm just saying it's not hard to imagine that their priorities don't include bugs which were obscure only a year ago.

pohl 17y ago
The specificity does not derive from my post, but from the source of the tests that you are arguing against being fixed, viewable by all, and well documented. The traversal tests seem like very reasonable cases to me. For example: // test 1: NodeFilters and Exceptions // test 2: Removing nodes during iteration // test 4: ignoring whitespace text nodes with node iterators // test 5: ignoring whitespace text nodes with tree walkers I just wanted to know if you had something in mind or were just making vague apologies for the IE team. Either case is ok with me.