Raphael Kubo da Costa

Just for the record, OSSystems/meta-browser#517 contains more information about hiccups people have hit due to libstdc++ being used in native builds. According to https://github.com/OSSystems/meta-browser/issues/517#issuecomment-869804396 libcxx-native is building fine now, but...

Nice to hear! Can you clarify what changes are needed where? https://github.com/YoeDistro/meta-browser/commit/d0436f6a4059e7d9f878ccdf4b9f031cee77b373 looks like an obvious candidate, but its commit message also mentions some changes in meta-clang.

Good. Is there a way to move those changes you've made to the chromium recipe back to meta-clang? That is, if one does something like `RUNTIME = "llvm"` or `RUNTIME_class-native...

Also, does it mean the changes you've landed to YoeDistro cannot land into the main meta-browser repo because it'd break compatibility with the other, non-master branches?

@r1mikey @TonyTascioglu fyi

> Interesting that some of the patches were still needed despite the llvm change. My uninformed guess is that the headers from the patches that are still necessary ended up...

For the record: I've recently landed a [patch](https://chromium-review.googlesource.com/c/chromium/src/+/3412476) in Chromium that makes `Sensor.start()` do nothing when the document is not fully active (strictly speaking, when there's no attached frame i.e....

I've been confused about this [before](https://github.com/w3c/web-nfc/issues/622#issuecomment-946023029) too, and I think the current text is fine as-is. The constructor algorithm is actually specified in the [DOM spec](https://dom.spec.whatwg.org/#concept-event-constructor): > When a constructor...

Thanks @domenic. #430 should make things a bit more clear. I guess it's too late to deprecate SensorErrorEvent though :/

I think this is also related to the discussions in the [DAS WG 2021 Q2 virtual meeting](https://www.w3.org/2021/04/08-dap-minutes.html#t01), where there was a resolution saying we would _"Make default allowlist "self" for...