[Webkit-unassigned] [Bug 43400] Add priority attribute to XMLHttpRequest

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Aug 3 10:51:12 PDT 2010


--- Comment #4 from James Simonsen <simonjam+webkit at google.com>  2010-08-03 10:51:12 PST ---
(In reply to comment #3)
> (From update of attachment 63294 [details])
> This should at least be behind an ifdef, so that platforms that ignore this flag wouldn't look like they honor it to JS code. Maybe this shouldn't be in WebKit trunk at all, as it's purely an experiment.

The proposal (http://www.belshe.com/test/xmlhttprequest.priorities.html) says it's safe to ignore:

"Browsers are not required to support the priority requested by applications, and may ignore it altogether."

I think it's fine that most WebKit implementations ignore it. Chrome will use it soon.

> +    const char* const names[5] = { "critical", "high", "normal", "low", "lowest" };
> Normally, constants are numbers, not strings. See e.g. XMLHttpRequest.readyState.

It's modeled after lineCap and lineJoin in the canvas tag. I think the thinking is that it'd be easier to add to or change the priorities later.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list