Closed
Bug 976654
Opened 10 years ago
Closed 10 years ago
frame should take `name` instead of `id`.
Categories
(Add-on SDK Graveyard :: General, defect, P1)
Tracking
(firefox28 unaffected, firefox29 fixed, firefox30 fixed)
RESOLVED
FIXED
mozilla30
Tracking | Status | |
---|---|---|
firefox28 | --- | unaffected |
firefox29 | --- | fixed |
firefox30 | --- | fixed |
People
(Reporter: irakli, Assigned: irakli)
Details
Attachments
(2 files)
46 bytes,
text/x-github-pull-request
|
zer0
:
review+
|
Details | Review |
5.33 KB,
patch
|
lsblakk
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
At the moment frame API optionally takes `id` property that is assumed to be unique, but it can not be, instead we should rename it to `name` and generate `id` that is guaranteed to be unique.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → rFobic
Comment 1•10 years ago
|
||
+1. For the case of frames specifically, how many frames would you see being created? is the uniqueness of the id scoped to the current add-on or all add-ons? How unique does the id need to be?
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8381551 -
Flags: review?(zer0)
Priority: -- → P1
Comment 3•10 years ago
|
||
Comment on attachment 8381551 [details] [review] Fix As discussed in IRC, I don't agree to renaming id in name now, without a proper discussion on how to change the High Level APIs. I would prefer instead fixing id and then introduce the new paradigm after properly discussed. However the code looks good, and for the rest of the team there is no particular issue to land this code, plus you're the module owner so the ultimate decision is up to you. So, r+. Please fill a bug to properly document the change in sdk/ui/frame before the uplift.
Attachment #8381551 -
Flags: review?(zer0) → review+
Comment 4•10 years ago
|
||
Comment on attachment 8381551 [details] [review] Fix As discussed in IRC, I don't agree to renaming id in name now, without a proper discussion on how to change the High Level APIs. I would prefer instead fixing id and then introduce the new paradigm after properly discussed. However the code looks good, and for the rest of the team there is no particular issue to land this code, plus you're the module owner so the ultimate decision is up to you. So, r+. Please fill a bug to properly document the change in sdk/ui/frame before the uplift.
Comment 5•10 years ago
|
||
Commit pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/02bde89bc9bd567afc85bff164592b37ead38d9b Merge pull request #1410 from Gozala/bug/frame-name@976654 Bug 976654 - Rename `options.id` to `options.name` and generate unique `id`. r=@zer0
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 6•10 years ago
|
||
[Approval Request Comment] Bug caused by (feature/regressing bug #): New UX widgets User impact if declined: API correctness fix. Taking this in 29 means developers who use the new APIs in 29 won't have to change their code in 30. Testing completed (on m-c, etc.): Landed in m-c in https://hg.mozilla.org/mozilla-central/rev/f65e5e3da415 Risk to taking this patch (and alternatives if risky): Low risk String or IDL/UUID changes made by this patch: None
Attachment #8391519 -
Flags: approval-mozilla-aurora?
Updated•10 years ago
|
Attachment #8391519 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 7•10 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/0071e789edce
status-firefox28:
--- → unaffected
status-firefox29:
--- → fixed
status-firefox30:
--- → fixed
Target Milestone: --- → mozilla30
You need to log in
before you can comment on or make changes to this bug.
Description
•