canmove, Confirmed users
901
edits
ExposureGuidelines: Difference between revisions
→TODO for this policy
| Line 45: | Line 45: | ||
# FIXMEs above | # FIXMEs above | ||
# set up a joint mailing list with Blink for intent to implement/ship (overholt is in contact with some Blink people) | # set up a joint mailing list with Blink for intent to implement/ship (overholt is in contact with some Blink people) | ||
# find a better example than window.navigator that we need to fix up with these guidelines in mind | |||
# keep track of progress towards standardization for in-development APIs (collaboration with Blink around something like chromestatus.com is a possibility) | # keep track of progress towards standardization for in-development APIs (collaboration with Blink around something like chromestatus.com is a possibility) | ||
# explicitly call out that API exposure for Firefox OS apps (ie. certified, packaged) doesn't fit into this policy? | # explicitly call out that API exposure for Firefox OS apps (ie. certified, packaged) doesn't fit into this policy? | ||
# evaluate effectiveness of guidelines, possibly considering a mechanism to limit exposure (ex. commit hook for all new WebIDL files) | # evaluate effectiveness of guidelines, possibly considering a mechanism to limit exposure (ex. commit hook for all new WebIDL files) | ||