Opened 11 years ago
Last modified 10 years ago
#4069 new defect
Browse: OSK not displayed in password entries
Reported by: | manuq | Owned by: | erikos |
---|---|---|---|
Priority: | Normal | Milestone: | Unspecified |
Component: | Sugar | Version: | 0.97.x |
Severity: | Major | Keywords: | 13.1.0, upstream |
Cc: | tonyforster, erikos, dsd, humitos | Distribution/OS: | OLPC |
Bug Status: | Unconfirmed |
Description
TestCase:
- open Browse with the laptop in ebook mode
- go to bugs.sugarlabs.org and tap 'login'
in the login form, the osk is displayed for the name field, but not for the password field.
Attachments (1)
Change History (19)
Changed 11 years ago by tonyforster
comment:1 Changed 11 years ago by tonyforster
- Cc tonyforster added
comment:2 Changed 11 years ago by dsd
comment:3 Changed 11 years ago by humitos
I added a new comment on this issue on WebKit: https://bugs.webkit.org/show_bug.cgi?id=84875
comment:4 Changed 11 years ago by humitos
I found the correct bug report (on WebKit) that deals with this specific issue:
comment:5 Changed 11 years ago by humitos
- Cc erikos dsd added
Simon, Daniel: I'd like to let you know about the state of this issue, that's why I'm CC you.
I've found a bug on the GTK version of WebKit that has to do with this issue (see my previous comment). There is a patch on the webkit ticket but it mention some security concerns. Should we move it out from 0.98?
comment:6 Changed 11 years ago by humitos
- Cc humitos added
comment:7 Changed 11 years ago by erikos
- Bug Status changed from Unconfirmed to Assigned
- Distribution/OS changed from Unspecified to OLPC
- Keywords triage added
I think this one is important, I bumped into it myself #4207 when trying to finish my test case http://wiki.sugarlabs.org/go/Features/Touch/Testing#File_a_bug_in_bugs.sugarlabs.org
This one should be bumped up in priority.
comment:8 Changed 11 years ago by manuq
- Priority changed from Unspecified by Maintainer to Urgent
- Severity changed from Unspecified to Major
comment:9 Changed 11 years ago by manuq
- Keywords triage removed
comment:10 Changed 11 years ago by erikos
Building webkitgtk3 with upstream patch to see if that fixes the issue: http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1250647
comment:11 Changed 11 years ago by erikos
Ok, I just verified that the issue is on the WebKitGtk side.I just logged in to the bug tracker in ebook mode to comment :)
comment:12 Changed 11 years ago by erikos
I commented on the upstream bug. Looks like a shame to not have this fixed, especially because there is already a simple patch and things got stuck in the review loop at one point.
comment:13 Changed 11 years ago by erikos
- Keywords upstream added
- Milestone changed from 0.98 to 1.0
This can only be solved upstream.
I did another nag: http://lists.webkit.org/pipermail/webkit-gtk/2012-November/001300.html
Moving this one out, as it is not in our hands. I will keep on nagging.
comment:14 Changed 10 years ago by mikhas
This is reported as a critical bug in Maliit, too:
https://bugs.maliit.org/show_bug.cgi?id=89
Instead of reporting the bug against Webkit, we had chosen to report it against the browsers itself:
https://bugzilla.mozilla.org/show_bug.cgi?id=749123 (Firefox)
https://code.google.com/p/chromium/issues/detail?id=125161 (Chromium)
That didn't have much success either, however.
On the Maliit mailing list, this issue is coming up again, but this time it's not working with *any* input field in web views:
http://lists.maliit.org/pipermail/maliit-discuss-maliit.org/2013-June/000330.html
Christian Dywan provided a patch here, but it's over 2 years old by now:
https://bugs.webkit.org/show_bug.cgi?id=34285#c6
comment:15 Changed 10 years ago by dnarvaez
- Bug Status changed from Assigned to New
comment:16 Changed 10 years ago by dnarvaez
- Milestone changed from 1.0 to Unspecified
comment:17 Changed 10 years ago by dnarvaez
- Bug Status changed from New to Unconfirmed
comment:18 Changed 10 years ago by dnarvaez
- Priority changed from Urgent to Normal
Nobody claimed this at an OLPC triage meeting - it might not be fixed for 13.1.0.