Closed
Bug 1027787
Opened 12 years ago
Closed 12 years ago
Report unique device name from discovery
Categories
(DevTools Graveyard :: WebIDE, defect)
DevTools Graveyard
WebIDE
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 33
People
(Reporter: jryans, Assigned: jryans)
References
Details
Attachments
(1 file, 4 obsolete files)
|
6.72 KB,
patch
|
jryans
:
review+
|
Details | Diff | Splinter Review |
Device discovery currently uses the host name / Android device name as the device name it sends out, which then appears in the runtime list.
If you have multiple devices with the same name, then there's no way to tell them apart at the moment. Should more info to the name or something to help discriminate. Or perhaps expose b2g version, etc.?
| Assignee | ||
Comment 1•12 years ago
|
||
Paul, this gives a more unique name on b2g, such as "flame-1234abcd", instead of just "flame".
This would become important anywhere there are many b2g devices on the same local network (like most Mozilla offices I would guess!).
Try: https://tbpl.mozilla.org/?tree=Try&rev=ef1e7e43fdc5
| Assignee | ||
Comment 2•12 years ago
|
||
Fix test failure.
Try: https://tbpl.mozilla.org/?tree=Try&rev=ee8184891aa7
Attachment #8452565 -
Attachment is obsolete: true
Attachment #8452565 -
Flags: review?(paul)
Attachment #8452670 -
Flags: review?(paul)
Comment 3•12 years ago
|
||
Comment on attachment 8452670 [details] [diff] [review]
Unique device discovery names for b2g (v2)
To get the settings, use "@mozilla.org/settingsService;1". For example: http://mxr.mozilla.org/mozilla-central/source/toolkit/devtools/server/actors/device.js#58
I'll finish the review next week.
Comment 4•12 years ago
|
||
Comment on attachment 8452670 [details] [diff] [review]
Unique device discovery names for b2g (v2)
Review of attachment 8452670 [details] [diff] [review]:
-----------------------------------------------------------------
::: toolkit/devtools/discovery/discovery.js
@@ +149,5 @@
> + */
> +function LocalDevice() {
> + this._name = LocalDevice.UNKNOWN;
> + if (window) {
> + this._settings = window.navigator.mozSettings;
As mentioned in previous comment, don't use `window`, but the service.
Attachment #8452670 -
Flags: review?(paul) → review+
| Assignee | ||
Comment 5•12 years ago
|
||
Updated to use SettingsService instead of mozSettings from a window.
Try: https://tbpl.mozilla.org/?tree=Try&rev=948a0af5e70d
Attachment #8452670 -
Attachment is obsolete: true
Attachment #8456853 -
Flags: review+
| Assignee | ||
Comment 6•12 years ago
|
||
Fixed test failure.
Try: https://tbpl.mozilla.org/?tree=Try&rev=fb38634547ef
Attachment #8456853 -
Attachment is obsolete: true
Attachment #8457407 -
Flags: review+
| Assignee | ||
Comment 7•12 years ago
|
||
More test failures fixed.
Try: https://tbpl.mozilla.org/?tree=Try&rev=5b9419529fed
Attachment #8457407 -
Attachment is obsolete: true
Attachment #8458105 -
Flags: review+
| Assignee | ||
Comment 8•12 years ago
|
||
Try is quite colorful, but looks like all issues were infra problems or known intermittents.
Keywords: checkin-needed
Comment 9•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 33
Updated•8 years ago
|
Product: Firefox → DevTools
Updated•6 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•