Emilio Cobos Álvarez
Emilio Cobos Álvarez
> I think could be fixed by computing static positions separately in the top layer. Not sure about that. You can have this case (abspos element in the top layer...
Well that's what this issue is about. The dependency comes from the static position, because that is usually "the position the box would have if not abspos" (and thus if...
I'm confused, so in chrome the top-layer reparenting also reparents the regular in-flow position? That is... not what I'd expect... I mean, that makes the static position rather useless I...
Basically that the static position doesn't reflect the position the element would have if not top layered (which is what WebKit and Gecko do). It moves the static position to...
@fantasai looks good!
@domenic @annevk Ok I just removed those tests for now. Those tests would also not be correct if we removed the `XMLDocument` interface (because they would do `instanceof undefined`).
(`instanceof Document` is tested in `checkMetadata`)
Alright, done!
Ah I guess the warning is not quite related to the protocol error.
WAYLAND_DEBUG is useful: ``` [2131796.835] -> wl_display#1.get_registry(new id wl_registry#2) [2131796.879] -> wl_display#1.sync(new id wl_callback#3) [2131797.012] {Display Queue} wl_display#1.delete_id(3) [2131797.048] wl_registry#2.global(1, "wl_compositor", 6) [2131797.076] -> wl_registry#2.bind(1, "wl_compositor", 5, new id [unknown]#4)...