Closed Bug 1497450 Opened 6 years ago Closed 6 years ago

[remote-dbg-next] Navigating to a new URL on USB device should be reflected in about:debugging

Categories

(DevTools :: about:debugging, enhancement, P1)

enhancement

Tracking

(firefox66 verified, firefox67 verified, firefox68 verified)

VERIFIED FIXED
Firefox 66
Tracking Status
firefox66 --- verified
firefox67 --- verified
firefox68 --- verified

People

(Reporter: jdescottes, Assigned: daisuke)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

STRs:
- enable new about:debugging
- connect a USB device with a tab open on URL1
- connect to the device on about:debugging and select it
- verify that URL1 is displayed in the targets
- on the device, navigate to URL2

=> about:debugging is not updated.

Note that if you add/remove a tab on the device, then about:debugging updates (and will show up to date URLs for all tabs)
Priority: P3 → P2
Assignee: nobody → dakatsuka
Status: NEW → ASSIGNED
Priority: P2 → P1
Currently, when `about:debugging` is displaying, even if move to another URL on
Android, its update does not reflect to `about:debugging` page. Because we
assumed that the `DOMTitleChanged` event comes from only XUL. In this patch,
get the event from BrowserApp on Android, then notify to clients.
This is another approach of D12094.
As advice in D12873, we already had a mechanism to notify the title changes
event in case of not remote browser[1]. In this patch, to use the mechanism,
fire `TabAttrModified` event from browser of Android when that got
`DOMTitleChanged` event.

Depends on D12873
Attachment #9028160 - Attachment is obsolete: true
Pushed by dakatsuka@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3b599381681e
Get DOMTitleChanged event of Android from DevTools server. r=ochameau,jdescottes
https://hg.mozilla.org/mozilla-central/rev/3b599381681e
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 66

Verified as fixed on Firefox Nightly 68.0a1 (2019-04-01), Firefox 67.0b6 and Firefox 66.0.2 on Windows 10 x 64, Windows 7 x32, Mac OS X 10.14 and on Ubuntu 16.04 x64.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: