JEP Context menu 2

Context menu API has a a notion of content scripts which are pretty exceptional, in the way they work. They are also problematic since API is incompatible with any kind of environment where content and chrome are isolated environments. Will be referring to such environment E10S without implying multi process architecture. Some signs of this has already being observable in attempts in porting context-menu API to Fennec.

As a matter of fact current API is even problematic for the current environment and set of workarounds are in place in a code that deals with content scripts:

1. Context menu implementation passes DOM nodes between chrome and content that isn't compatible with E10S. It is also implies certain security concerns.
2. Context menu's requires blocking calls from chrome to content, which is also incompatible with E10S.

All of the above are signs that porting this API to new platforms will be problematic, so it's better to revisit design earlier than later.

Goals

• New API should address majority of use cases that users have.
• New API should simplify simple cases.
• New API should not have content scripts.

Not a goals

• New API is not supposed to address every use case, same as SDK.