Closed Bug 1552806 Opened 7 months ago Closed 6 months ago

[remote-dbg-next] Setup page intro text should not mention "tabs" category for "This Firefox"

Categories

(DevTools :: about:debugging, defect, P3)

defect

Tracking

(firefox69 fixed)

RESOLVED FIXED
Firefox 69
Tracking Status
firefox69 --- fixed

People

(Reporter: jdescottes, Assigned: francis.houle+bugzilla, Mentored)

References

(Blocks 1 open bug)

Details

(Keywords: good-first-bug)

Attachments

(1 file)

STRs:

  • go to about:debugging#/setup
  • read the "Setup" section

The intro text for about:debugging's Setup page contains:

Use This Nightly to debug tabs, extensions and service workers on this version of Nightly.

However, by default we don't enable Tab debugging for the local This Firefox/This Nightly. We should update this string accordingly.

Use This Nightly to debug tabs, extensions and service workers on this version of Nightly. should become Use This Nightly to debug extensions and service workers on this version of Nightly.

The string is defined in aboutdebugging.ftl#105

When updating a localized string, you also need to update the name of the string. So here about-debugging-setup-this-firefox should be changed, for instance to about-debugging-setup-this-firefox2. And then we should update the component referring to this string ConnectPage.js#267

Hello Julian,
I would like to work on this.
Could it be assigned to me?

Thanks!

(In reply to Tushar Narkhede from comment #1)

Hello Julian,
I would like to work on this.
Could it be assigned to me?

Sorry Tushar, I missed your message :(
Francis already attached a patch here, so I will assign the bug to them.

Assignee: nobody → francis.houle+bugzilla
Status: NEW → ASSIGNED
Priority: -- → P3
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/885a43de081b
Remove 'tabs' mention from setup page intro text. r=jdescottes,flod
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 69
QA Whiteboard: [qa-69b-p2]
You need to log in before you can comment on or make changes to this bug.