ASSIGNED 237047
Refactor DOMWindow calls generating console warnings into a single DOMWindow::printWarningMessage method
https://bugs.webkit.org/show_bug.cgi?id=237047
Summary Refactor DOMWindow calls generating console warnings into a single DOMWindow:...
Tim Nguyen (:ntim)
Reported 2022-02-22 11:42:01 PST
Attachments
Patch (5.12 KB, patch)
2022-02-22 13:08 PST, Tim Nguyen (:ntim)
darin: review+
[fast-cq] Patch (5.14 KB, patch)
2022-02-22 21:58 PST, Tim Nguyen (:ntim)
no flags
Tim Nguyen (:ntim)
Comment 1 2022-02-22 13:08:36 PST
Darin Adler
Comment 2 2022-02-22 15:59:16 PST
Comment on attachment 452896 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=452896&action=review > Source/WebCore/page/DOMWindow.h:273 > + void printConsoleMessage(const String&, MessageLevel) const; > void printErrorMessage(const String&) const; > + void printWarningMessage(const String&) const; Can these all be private? Is there any caller using them outside the class?
Tim Nguyen (:ntim)
Comment 3 2022-02-22 21:58:40 PST
Created attachment 452937 [details] [fast-cq] Patch
EWS
Comment 4 2022-02-22 22:02:27 PST
Committed r290348 (247666@main): <https://commits.webkit.org/247666@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 452937 [details].
Radar WebKit Bug Importer
Comment 5 2022-02-22 22:03:17 PST
Robert Jenner
Comment 6 2022-02-23 16:39:40 PST
Reverted r290348 for reason: Broke a test, slowing down EWS. Committed r290399 (247711@trunk): <https://commits.webkit.org/247711@trunk>
Dawn Morningstar
Comment 7 2022-02-23 16:49:35 PST
Robert reverted r290348 for me as I do not have committer status yet. https://bugs.webkit.org/show_bug.cgi?id=237116 Change seems to have broken "lastConsoleMessage" As it no longer sees the warning.
Darin Adler
Comment 8 2022-02-23 17:56:45 PST
Turns out there is a debugging feature, Document::setConsoleMessageListener, used for regression tests, that only works with messages sent to the console client through the document. And there was a test depending on using this mechanism to see the console messages from startListeningForDeviceOrientationIfNecessary and startListeningForDeviceMotionIfNecessary. Outside of the tests, there was nothing wrong with this, but it broke the tests. Sadly this means that we have to replace Document::setConsoleMessageListener with a better testing mechanism or keep these messages flowing through the document. My fault for suggesting that we didn’t need to send the messages through the document. Turns out not to be true for this exotic test-only reason.
Darin Adler
Comment 9 2022-02-24 09:12:25 PST
I’ll do this.
Note You need to log in before you can comment on or make changes to this bug.