Closed Bug 1006343 Opened 11 years ago Closed 11 years ago

Cannot enable layouts with keyboard setup menu after 3rd-party keyboard installation

Categories

(Firefox OS Graveyard :: Gaia::System::Input Mgmt, defect)

x86
macOS
defect
Not set
normal

Tracking

(blocking-b2g:2.0+, b2g-v2.0 fixed)

RESOLVED FIXED
2.0 S2 (23may)
blocking-b2g 2.0+
Tracking Status
b2g-v2.0 --- fixed

People

(Reporter: rudyl, Assigned: rudyl)

References

Details

(Keywords: regression, Whiteboard: [p=1])

Attachments

(2 files)

STR === 1. Install "LOL keyboard" from marketplace. 2. After installation is complete, the system should pop up setup menu. 3. Enable "\o/" layout. 4. Launch the keyboard via any input field. Expected result: The new layout has been enabled and ready to use. Actual: Could not see the new layout enabled.
Since this is also a functional regression, nominate it as 2.0+.
Blocks: 964670
blocking-b2g: --- → 2.0?
blocking-b2g: 2.0? → 2.0+
Hey guys, is this blocking all third party keyboard support?
Looks like you can still enable by going through settings > keyboards etc. Just the prompt doesn't change the active keyboard.
Tested with Buri. This issue is reproducible on today's master, and reproducible on today's 1.4, but on today's 1.3, the keyboard cannot be successfully installed. After tapping on 'Install' on marketplace, the device does nothing, and in Settings it doesn't look like it's been installed either. So I went back to: 20131212040203 master build - can't install keyboard 20131220040201 master build - can't install keyboard 20131230040201 master build - issue reproduces 20140112040202 master build - issue reproduces My question is: Is this really a regression?
The feature is disabled on 1.3 & 1.4, so that's why this isn't working there. The window needs to be analyzed on trunk here, as that's the only place where the feature was enabled.
If I understand correctly, I will be looking for a window between can't install & broken installation on master?
(In reply to Pi Wei Cheng from comment #6) > If I understand correctly, I will be looking for a window between can't > install & broken installation on master? Nope - you should be looking for a window when this was last working on master, first broken on master.
(In reply to Jason Smith [:jsmith] from comment #7) > Nope - you should be looking for a window when this was last working on > master, first broken on master. My testing shows that this has never worked. Attaching a txt worksheet of all the builds I went through and their results. JZimbrick wants me to find the window between "Last Can't Install" and "First Broken Installation" anyway. So here it is. b2g-inbound window: Last Can't Install Environmental Variables: Device: Buri MOZ BuildID: 20140318202202 Gaia: 854f8d91d77fb1364683bf909f7605c185043c8e Gecko: 38a3545c5a6c Version: 31.0a1 Firmware Version: v1.2-device.cfg First Broken Installation Environmental Variables: Device: Buri MOZ BuildID: 20140319000201 Gaia: db2ef2b61c70889533a0837fa3e053d24e95fdea Gecko: a6476baa3307 Version: 31.0a1 Firmware Version: v1.2-device.cfg Last Can't Install Gaia / First Broken Installation Gecko: Can't Install Keyboard Gaia: 854f8d91d77fb1364683bf909f7605c185043c8e Gecko: a6476baa3307 Last Can't Install Gecko / First Broken Installation Gaia: Issue DOES reproduce Gaia: db2ef2b61c70889533a0837fa3e053d24e95fdea Gecko: 38a3545c5a6c Gaia Pushlog: https://github.com/mozilla-b2g/gaia/compare/854f8d91d77fb1364683bf909f7605c185043c8e...db2ef2b61c70889533a0837fa3e053d24e95fdea
Assignee: nobody → rlu
Whiteboard: [p=1]
Target Milestone: --- → 2.0 S2 (23may)
Status: NEW → ASSIGNED
This change make the IME install page invoke keyboard helper with manifestURL instead of app origin to enable a specific layout. Unit test is also updated. -- Gary, could you review this? Thanks.
Attachment #8421834 - Flags: review?(gchen)
Comment on attachment 8421834 [details] [review] Patch V1 - pull request 19199 looks good for me, r=garychen. Thanks~
Attachment #8421834 - Flags: review?(gchen) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
We don't have integration test yet to cover this feature, and will track this work with bug 1010021.
Flags: in-testsuite?
Has been covered by the test added in bug 1010021.
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: