Closed
Bug 1092122
Opened 10 years ago
Closed 7 years ago
Add detection of contenteditable, and support rich text input methods
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
INCOMPLETE
tracking-b2g | backlog |
People
(Reporter: dietrich, Unassigned)
References
Details
(Whiteboard: [FT:System-Platform])
Attachments
(1 file)
(deleted),
image/png
|
Details |
An advantage of our keyboards being Web content is that richness of content on the web can be expressed as inputs. The explosion of popularity of emoji and "stickers" are examples of this. However they're limited to either restricted character sets or control by proprietary applications. If our keyboard APIs supported rich content, we can use the Web to do amazing things to advance the human race: * Keyboards comprised of images from your contacts. * Dynamic keyboards from gif websites which update live content with the most popular gifs. * Keyboards where all keys are pictures of cute kittens. The options are limited only by imagination and sanity. I have attached an example of a prototype keyboard app that I wrote, where each key is a picture of Kanye West's face, so you can express yourself through all the dimensions of his moods and personality.
Comment 1•10 years ago
|
||
LOL that image is funny. None the less I think this API need careful security design accompany with the proposal. Keyboard app certainly shouldn't insert <script> into the node. Even injecting <img> could create privacy issue if images are loaded from remote sites.
Blocks: keyboard-api
blocking-b2g: --- → backlog
Component: Gaia::Keyboard → DOM: Device Interfaces
Product: Firefox OS → Core
Whiteboard: [FT:System-Platform]
Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Comment 2•7 years ago
|
||
Cleaning up Device Interfaces component, and mass-marking old FxOS bugs as incomplete. If any of these bugs are still valid, please let me know.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•