-
```
What steps will reproduce the problem?
1. try to call "canvas.toDataURL()"
What is the expected output? What do you see instead?
Expected : a PNG export of canvas data
Instead : function does not…
-
```
What steps will reproduce the problem?
1. try to call "canvas.toDataURL()"
What is the expected output? What do you see instead?
Expected : a PNG export of canvas data
Instead : function does not…
-
Blocks #5601.
- Spec: https://encoding.spec.whatwg.org/#concept-td-serialize.
- Code: (probably) `components/script/dom/textdecoder.rs`.
- Test: `/encoding/textdecoder-byte-order-marks.html`.
-
Code: `components/script/dom/xmlhttprequest.rs`
Spec: https://xhr.spec.whatwg.org/#document-response
Test: `tests/wpt/web-platform-tests/XMLHttpRequest/responsexml-*.htm`
cc @liviuba
-
In the light of https://github.com/servo/servo/pull/24148
This will be soon relevant: https://github.com/whatwg/html/pull/4115
cc @asajeffrey
-
Similar to #5414 (about tabindex="0" and interactive content) but with less compat constraints.
Currently in the spec and in Chromium form-associated custom elements are not treated as interactive …
-
According to the HTML standard (https://html.spec.whatwg.org/multipage/webappapis.html, Section 8.1.3.10), a worker of any type and a shared worker are not within the same agent cluster, and thus cann…
dpino updated
6 years ago
-
(reposted here: initially posted on https://github.com/whatwg/html/issues/5696; but this was closed without any discussion even though I was reading and commenting a draft page of the WHATWG group!)
…
-
With the deprecation of the `:--state` syntax, I imagine the restrictions around requiring the `--` prefix should be removed.
https://groups.google.com/a/chromium.org/g/blink-dev/c/GDmNaxAuCY4/m/WO…
-
comeon man async dat ish
> Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org…