Andreu Botella

I'm not a Unicode expert by any means, but I don't think that's accurate. Clearly the U+FFFD code point must be able to be used in a meta sense, to...

Since a surrogate is defined as being a code point, not a code unit, the very presence of the word "surrogate" in that algorithm automatically implies that the string must...

Infra's "surrogate" corresponds to Unicode's "surrogate code point" (not to Unicode's "surrogate pair"). Now, Infra doesn't have a definition of "surrogate pair", but the usages in non-normative text corresponds to...

I'm looking at the various usages of the Encoding hooks across several standards, and they seem to be called almost every time with a byte sequence (respectively, with a string),...

I think we might want to define that types which are a wrapper over some other type should by default have conversions to/from that wrapped type, but we might want...

There's also the fact that this section uses the terms "keyword mapping" and "property mapping", which aren't defined anywhere. While keyword mappings would seem simple enough (don't map them at...

With [bug 1661075](https://bugzilla.mozilla.org/show_bug.cgi?id=1661075) fixed, the logos are now showing up on Firefox Nightly. Note that this fix wasn't related to preload at all, it just changed `` to support the...

I have the same problem in the content of `` elements: ```jsx const React = require("react"); const ReactDOMServer = require("react-dom/server"); console.log(ReactDOMServer.renderToStaticMarkup( {` html { font-family: "Source Sans Pro", sans-serif; }...

In the WinterCG meeting it was also mentioned that making `cause` a property in the prototype might go against the [priority of constituencies](https://w3ctag.github.io/design-principles/#priority-of-constituencies), since the `cause` property in `Error` instances...

From my tests, it seems like all browser engines honor `display: none` on `` elements; and they will not render anything for `display: contents`, [even if the `` element has...