Closed Bug 816869 (3rd-party-keyboard) Opened 12 years ago Closed 10 years ago

[Meta] Enable third-party keyboards

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::Keyboard
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(feature-b2g:-)

Status:
RESOLVED FIXED
Project Flags:
feature-b2g -

People

(Reporter: rudyl, Unassigned)

References

Details

(Whiteboard: [tech-p1], ux-tracking, [dependency: marketplace-partners])

** For V2 - Keyboard ** In V1, the built-in virtual keyboard is a single web app. which is embedded in a mozBrowser/mozApp iframe of Gaia system app. (but not OOP) As Open Web platform, we want to enable that the users can install 3rd-party keyboard app to Firefox OS. This is a meta bug created to track the work we need to achieve that goal.
OS: Mac OS X → All
Hardware: x86 → All
Please refer bug 816905 to know how's going on Gaia.
Alias: 3rdkeyboard
Summary: [Keyboard] Enable 3rd-party Keyboard Support → [meta][Keyboard] Enable 3rd-party Keyboard Support
Alias: 3rdkeyboard → 3rd-party-keyboard
Depends on: 838547
This is more of work for gecko than gaia, but it doesn't particularly matter to me which component we track it from.
Needed for competitive parity and to not lock users into default gaia keyboard.
Whiteboard: [tech-p1]
Depends on: 847763
Whiteboard: [tech-p1] → u=user c=keyboard s=ux-most-wanted, [tech-p1]
OS: All → Gonk (Firefox OS)
QA Contact: wachen → whsu
Hardware: All → ARM
Whiteboard: u=user c=keyboard s=ux-most-wanted, [tech-p1] → [tech-p1] u=user c=keyboard s=ux-most-wanted
Summary: [meta][Keyboard] Enable 3rd-party Keyboard Support → [Meta] Enable third-party keyboards
Depends on: 856910
Depends on: 858383
Whiteboard: [tech-p1] u=user c=keyboard s=ux-most-wanted → [tech-p1], ux-tracking
Depends on: 885692
Depends on: 906598
No longer depends on: 906598
Depends on: 906614, 906617
Depends on: 909124
Depends on: 912951
Depends on: 941627
Depends on: 941885
Depends on: 968991
Whiteboard: [tech-p1], ux-tracking → [tech-p1], ux-tracking[dependency: marketplace-partners]
blocking-b2g: --- → 2.1?
feature-b2g: --- → -
adam - this has been a request for quite some time (see bug opened date) how do we nom this work as a product feature for 2.1 release? the feature nom field is blank. can you tell me what fxos product manager represents this feature area? caitlin
Flags: needinfo?(arogers)
Whiteboard: [tech-p1], ux-tracking[dependency: marketplace-partners] → [tech-p1], ux-tracking, [dependency: marketplace-partners]
Adding Bruce, who handles keyboards as part of System Platform and can speak to this specifically. In general, though, we have concluded 2.1 scoping and it's currently being cut even further, due to Tako and the condition of 2.0 but Bruce can speak to priority.
Flags: needinfo?(arogers) → needinfo?(bhuang)
This is actually landed in 2.0. The remaining piece to enable this was making sure keyboards run fine OOP: https://bugzilla.mozilla.org/show_bug.cgi?id=964670
Flags: needinfo?(bhuang)
It is concerning that there such a confusion about this in the gaia team. Does this bug not get resolved as fixed because it is Meta?
This is considered fixed already.
Status: NEW → RESOLVED
blocking-b2g: 2.1? → ---
Closed: 10 years ago
Resolution: --- → FIXED
harald - do you have apps to test with? is this working for our apps partners?
Flags: needinfo?(hkirschner)
No, partners were blocked on having this landed and a Simulator to test with. Nick works with them.
Flags: needinfo?(hkirschner) → needinfo?(nick)
Partners are unblocked. This can be verified with one of the test keyboards in Gaia.
Flags: needinfo?(nick)
You need to log in before you can comment on or make changes to this bug.