When displaying content in a captive portal, we should make sure the experimental <model> element is unavailable.
<rdar://90562002>
Created attachment 455260 [details] Patch
Comment on attachment 455260 [details] Patch r=me
Comment on attachment 455260 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=455260&action=review > Tools/TestWebKitAPI/Tests/WebKitCocoa/ProcessSwapOnNavigation.mm:7825 > + EXPECT_EQ(runJSCheck("!!window.HTMLModelElement"_s), shouldBeEnabled == ShouldBeEnabled::Yes); // Push API. The comment is wrong.
Comment on attachment 455260 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=455260&action=review >> Tools/TestWebKitAPI/Tests/WebKitCocoa/ProcessSwapOnNavigation.mm:7825 >> + EXPECT_EQ(runJSCheck("!!window.HTMLModelElement"_s), shouldBeEnabled == ShouldBeEnabled::Yes); // Push API. > > The comment is wrong. Ugh! Thank you for catching that.
Created attachment 455267 [details] Patch for landing
Committed r291579 (248679@main): <https://commits.webkit.org/248679@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 455267 [details].