Andrew Kaster
Andrew Kaster
Your changes cause numerous test failures in the LibWeb tests. Please take a look locally, and ask on discord if you're not sure how to run the tests ``` ==================================================...
If GHA supports VS Preview, I have no qualms about using that. That's what I've been using the entire time to test changes.
Anything that's more complicated than "use what's already there" or "Wait two weeks" seems not a good use of time.
The root cause of this imo is that in Page::load, we pass the active document of the current top level traversible as the source document for the navigation. This is...
For posterity, the "spec issue to complain in" relevant to this change is https://github.com/WebAssembly/spec/issues/1549
@xtremekforever if my example worked, I wouldn't mind taking a crack at cleaning it up for use in your examples here. However, it doesn't quite build and I don't know...
Also iirc I filed https://github.com/swiftlang/swift/issues/80570 while playing with this example. Evan's CMake scripts attempt to extract information about target-specific include dirs and lib dirs from `swiftc -print-target-info`. But this completely...
This is known and fixed on swiftlang/swift/main. We need main until the next release.
I've been using swiftly to install a main-snapshot. https://github.com/swiftlang/swiftly
Ladybird is not ready for general user testing. If there's a way to put a package behind a "please only use it you're planning to contribute upstream" flag, them sure,...