Xidorn Quan

Consider forbidding <frame> element from entering fullscreen

4

It seems that `` element is not allowed to be out-of-flow, so it's incompatible with the top layer model, like internal SVG and MathML elements. And it is a deprecated...

Propose to always render elements in the top layer as if it is fixed positioned

19

The current spec explicitly states that elements in the top layer may have `position: absolute` and in which case, it's containing block would be the initial containing block. If I...

Removing `:fullscreen-ancestor` pseudo-class causes webcompat issue

4

Gecko [unshipped `:-moz-full-screen-ancestor`](https://bugzilla.mozilla.org/show_bug.cgi?id=1199529) in Firefox 50, and recently it was reported to [cause breakage on Vimeo](https://bugzilla.mozilla.org/show_bug.cgi?id=1396732). In this specific case, there are three different behaviors among Gecko (before regression), Gecko...

Document state change should be synced with dimensions change

8

The current implementation in Gecko is that, the document state (document flag, element state, etc.) is changed immediately when the dimension gets changed. It doesn't really match the current spec....

Exit fullscreen on document with multiple subdocument in fullscreen

8

Assuming we have tree like: ``` body (document) | +- iframe #fa | | | +- div #a | +- iframe #fb | +- div #b ``` If we do:...

-webkit-text-fill-color and list marker

5

See the following code: ```html :root { color: red; -webkit-text-fill-color: green; } li::before, li::after { content: "##"; } hello hello ``` Should the list markers use `color` or `-webkit-text-fill-color`? Currently...

From the code, it seems that this crate would push forward the strategy wait time regardless of whether the service has restored. If a service just intermittently fail, this doesn't...

Update object safety to match impl around self as receiver

6

This fixes #1247.

Rule around non-dispatchable functions doesn't match the compiler behavior

5

In the [Object Safety section](https://doc.rust-lang.org/reference/items/traits.html#object-safety), it says: > * Explicitly non-dispatchable functions require: > * Have a `where Self: Sized` bound (receiver type of `Self` (i.e. `self`) implies this). This...

For example, the code in the README would be: ```js function createObservableUser(dbUserRecord) { return fromResource( (sink) => { // sink the current state sink(dbUserRecord.fields) // subscribe to the record, invoke...