Emilio Cobos Álvarez
Emilio Cobos Álvarez
Thanks for the report! For macro definitions we use `cexpr`, and it only provides an `EvalResult::Int`, so we choose a type based on the value. We have a way to...
Yep, this looks like it should go to rust-bindgen, and yeah you can point it to the toolchain location if you can point clang to it :)
I don't have write permission to this repo, can you merge this @andruud ?
Here's a test-case. One quirk here is that at least Blink and Gecko parse `*:hover` and `:hover` to exactly the same thing. So ignoring that `*` special-case, yes, I think...
> I think the only reason `::part(name)` has been designed as it is to avoid author names impeding with future built-ins. > The syntax could have been `::--name` fwiw. Citation...
> We could just allow pseudo-elements to be used in exportparts, like ``. I think that'd be super weird, to target something sometimes as part and sometimes as pseudo-element. Also...
> 1. While it is true we are not taking away names web developers can use, it is still utterly confusing. I'm not sure I agree, it is confusing the...
Ok, so things that I want discussed after chatting with @smaug---- (putting here for reference and so I don't forget): * API consistency (`::pseudo` is more consistent with _existing_ built-ins)....
I agree with @andruud that requiring two styling passes is a no-go. It's also cyclic, even though if you restrict the pseudo-class / at-rule to the UA sheet you can...
cc @chrishtr and @zcorpan who were also in that conversation.