Closed Bug 1237475 Opened 10 years ago Closed 10 years ago

about social error needs to use origin attributes properly

Categories

(Firefox Graveyard :: SocialAPI, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: huseby, Assigned: huseby)

References

Details

(Whiteboard: [userContextId][OA])

Attachments

(1 file)

in the file browser/base/content/aboutSocialError.xhtml there's this code: > 56 if (!config.origin) { > 57 let URI = Services.io.newURI(url, null, null); > 58 config.origin = > 59 Services.scriptSecurityManager.createCodebasePrincipal(URI, {}).origin; > 60 } this needs to create a default context origin attribute from the origin and then use that when creating the codebase principal.
Status: NEW → ASSIGNED
Whiteboard: [userContextId]
Attachment #8709199 - Flags: review?(mixedpuppy)
TBH, I don't see the need here, this is just using a principle to get the origin (a string). The principle instance isn't even held onto. How are the attrs going to change the origin?
Flags: needinfo?(huseby)
Flags: needinfo?(huseby)
Attachment #8709199 - Flags: review?(mixedpuppy)
After looking deeper into this, we do not want any of the origin attributes to transmit into the use of createCodebasePrincipal. Shane you're right, it's just getting the origin. If we add origin attributes to it, you'll get an origin with a suffix which it will then try to parse, which is not what we want. Using the default {} origin attributes will give us the correct behavior since user context id will be assigned the default value.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Whiteboard: [userContextId] → [userContextId][OA]
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: