Page MenuHomePhabricator

Fix the DarkConsole inline error log stack trace expansion behavior for Content-Security-Policy
ClosedPublic

Authored by epriestley on Mar 13 2018, 11:39 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 11, 8:49 AM
Unknown Object (File)
Thu, Apr 11, 8:37 AM
Unknown Object (File)
Sat, Apr 6, 4:46 AM
Unknown Object (File)
Sun, Mar 31, 7:32 AM
Unknown Object (File)
Sun, Mar 31, 2:32 AM
Unknown Object (File)
Sun, Mar 31, 2:32 AM
Unknown Object (File)
Sun, Mar 31, 2:32 AM
Unknown Object (File)
Mar 10 2024, 7:08 PM
Subscribers
None

Details

Summary

See PHI451. Ref T13102. DarkConsole uses an ancient inline "onclick" handler to expand the stack traces for errors.

The new Content-Security-Policy prevents this from functioning.

Replace this with a more modern behavior-driven action instead.

Test Plan
  • Clicked some errors in DarkConsole, saw stack traces appear.
  • Grepped for onclick and jsprintf() to see if I could find any more of these, but came up empty.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Mar 13 2018, 11:45 PM
This revision was automatically updated to reflect the committed changes.