1324688 - WE API proposal: Add an ability to get/set the status text and receive notification when the status text is about to change

Status: RESOLVED WONTFIX

(WebExtensions :: Untriaged, defect)

Description

[Masatoshi Kimura [:emk]]

This is required to implement add-ons such as Link Status Redux. Currently legacy add-ons replace setOverLink to achieve this.

Comment 1

[Caitlin Neiman [:caitmuenster]]

This has been added to the March 7 WebExtensions Triage mtg. agenda. 

Agenda: https://docs.google.com/document/d/1zzfedbTKAHUmm4UctxSOIJV3iKayXQ8TuXPodXW8wC0/edit#

Comment 2

[Kris Maglione [:kmag]]

We discussed this, and came to the conclusion that it's not worth the complexity it would entail, particularly as the status line has become less prominent in recent years, and related features like `window.status` have been disabled.

If you need this sort of functionality, please consider showing the information with an in-content UI instead.

Comment 3

[Timvde]

To get in some extra weight: Status-4-Evar[1] is an add-on with ~140k users, which probably also needs an API like this. The use case for S4E is: hiding the default status pop-up, and moving it into a bottom toolbar. Having UI elements pop over the page is often very annoying.

[1] https://addons.mozilla.org/en-US/firefox/addon/status-4-evar/

Comment 4

[Masatoshi Kimura [:emk]]

(In reply to Kris Maglione [:kmag] (long backlog; ping on IRC if you're blocked) from comment #2)
> If you need this sort of functionality, please consider showing the
> information with an in-content UI instead.

For extensions like Link Status Redux, in-content UI would have a serious privacy issue because web pages can read the last visited date from the injected UI. Is there any way that content scripts can show a UI that is inaccessible from web pages?

Comment 5

[Masatoshi Kimura [:emk]]

(In reply to Masatoshi Kimura [:emk] from comment #4)
> (In reply to Kris Maglione [:kmag] (long backlog; ping on IRC if you're
> blocked) from comment #2)
> > If you need this sort of functionality, please consider showing the
> > information with an in-content UI instead.
> 
> For extensions like Link Status Redux, in-content UI would have a serious
> privacy issue because web pages can read the last visited date from the
> injected UI. Is there any way that content scripts can show a UI that is
> inaccessible from web pages?

Because the ni was not responsive, I found bug 1287590 myself and read your comment saying something like "Don't inject in-content UI because it is inherently danger."

Are you kidding?