Closed Bug 984432 Opened 10 years ago Closed 10 years ago

Make location input autocompletion CSP compatible

Categories

(Webmaker Graveyard :: Events, defect)

Product:
Webmaker Graveyard
Component:
Events
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: kate, Unassigned)

References

Details

(Whiteboard: [events] [july11] events2, icebox) 

Right now we are forced to use 'unsafe-eval' in our CSP rules because of the places API.

We might consider this solution:
http://stackoverflow.com/questions/12204715/load-places-api-library-from-chrome-extension

After that let's remove 'unsafe-eval' from the rules
Depends on: 981679
Assignee: nobody → kate
Status: NEW → ASSIGNED
Assignee: kate → gavin
Assignee: gavin → nobody
Whiteboard: events2, r3 → events2, icebox
Can I pick up this bug? Am I right that this https://github.com/mozilla/webmaker-events-2/blob/master/app/views/partials/event-form.html#L96 input should be linked to autocompletion js file?!
@ Gavin: is this still needed? Can Alexander help?
Flags: needinfo?(gavin)
Whiteboard: events2, icebox → [events] [june27] events2, icebox
The problem here is the Google autocomplete service. We'd need to switch to another location autocomplete service to fix this issue.
This is probably not a realistic option since we're pulling location metadata form Google as well. If we can find another service that provides all necessary metadata and provides autocompletion UI in a similar manner then I'm up for discussion. 

I'd recommend WON'T FIX.
Flags: needinfo?(gavin)
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
* Ok. Kate, can you re-open if you disagree / want to discuss this further?
Flags: needinfo?(kate)
Whiteboard: [events] [june27] events2, icebox → [events] [july11] events2, icebox
Flags: needinfo?(kate)
You need to log in before you can comment on or make changes to this bug.