Improve the Developer Tools notification

NEW
Unassigned

Status

enhancement
P3
normal
3 years ago
29 days ago

People

(Reporter: denschub, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

3 years ago
At the moment, due to platform limitations and/or our lack of understanding it, the Developer Tools notification is limited to letting developers know we changed something.

In version 2 of our addon, we should provide more details:

- A link to the webcompat/bugzilla issue which contains more information about the issue, how to resolve it, ...
- A link to instructions on how to disable the overrides, so developers are able to test their stuff
Reporter

Updated

3 years ago
See Also: 13082711307788
Add dependency to bug 1317772, if we can use way other than webextension in chrome mode to write notification to web console.
Reporter

Comment 2

3 years ago
Undoing that. Bug 1317772 is for the responsive design mode. :)
No longer blocks: rdm-web-compat
Reporter

Updated

2 years ago
Blocks: 1386807
Reporter

Updated

2 years ago
No longer blocks: 1386807

Dennis, what is the current state of devtools notifications when an intervention is active?

Type: defect → enhancement
Flags: needinfo?(dschubert)
Priority: -- → P3
Reporter

Comment 4

Last month

Unfortunately, it's more complicated after our webextension rewrite. In the case of JS injections, we can add a simple console.log() to our injection, because that JS is executed within the website itself. However, that does not work for CSS injections, or user agent overrides.

Running console.log() in the background script where UA overrides and injecting the CSS happens would result in the message being logged into the browser console. For our use case, this is pretty much useless, because web developers will not see the message there.

And unfortunately, there also is no way of "finding the proper console API to write directly to the tab", because of webextension framework limitations. The only way I can think of to do site-console logging at the moment is to add a content script into every single website, then pass some messages between the content script and the background script to see if any interventions got applied, and if so, log something to the console. However, this sounds like it will have a significant performance hit.

This needs more research, unfortunately. :(

Flags: needinfo?(dschubert)

Thanks for the reply Dennis.

Would a webext experimental API help us?

However, this sounds like it will have a significant performance hit.

We could measure this, I guess.

You need to log in before you can comment on or make changes to this bug.