[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-06-05 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 Krinkle krinklem...@gmail.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-06-05 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 --- Comment #12 from Gerrit Notification Bot gerritad...@wikimedia.org --- Related URL: https://gerrit.wikimedia.org/r/67082 (Gerrit Change Ic38992e04b5f3932cf18f2dfc217cd733196efb8) -- You are receiving this mail because: You are on the CC

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-06-04 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 --- Comment #11 from Gerrit Notification Bot gerritad...@wikimedia.org --- Related URL: https://gerrit.wikimedia.org/r/66993 (Gerrit Change Idc5f4a23a2709264d869a91d00873c4e187bc470) -- You are receiving this mail because: You are on the CC

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-05-28 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 James Forrester jforres...@wikimedia.org changed: What|Removed |Added Target Milestone|VE-deploy-2013-05-27

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-05-25 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 James Forrester jforres...@wikimedia.org changed: What|Removed |Added Assignee|krinklem...@gmail.com

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-05-25 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 Krinkle krinklem...@gmail.com changed: What|Removed |Added CC||krinklem...@gmail.com

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-05-14 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 Krinkle krinklem...@gmail.com changed: What|Removed |Added Target Milestone|--- |VE-deploy-2013-05-27

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-05-13 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 James Forrester jforres...@wikimedia.org changed: What|Removed |Added Blocks||48426 --

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-05-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 James Forrester jforres...@wikimedia.org changed: What|Removed |Added CC|

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2013-05-07 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 --- Comment #7 from James Forrester jforres...@wikimedia.org --- Having discussed this with Timo just now, ua-parser has now moved even further away from being appropriate for client-side use, so here's the new plan: * We will have some basic

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2012-10-01 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 --- Comment #6 from Krinkle krinklem...@gmail.com 2012-10-01 19:42:49 UTC --- I submitted a pull request to ua-parser just now. Once they merge it I'll add that as a new module and let VisualEditor use that instead. I should probably keep

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2012-09-19 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 --- Comment #5 from Krinkle krinklem...@gmail.com 2012-09-19 17:49:22 UTC --- I'll see if its possible to extend jQuery.client. Otherwise we may want re-consider replacing this module with something more solid. There's two major parsers I know

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2012-09-10 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 Trevor Parscal tpars...@wikimedia.org changed: What|Removed |Added AssignedTo|tpars...@wikimedia.org

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2012-08-22 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 --- Comment #3 from Trevor Parscal tpars...@wikimedia.org 2012-08-22 22:03:37 UTC --- Now that bug 38857 is fixed, this is easy... Or is it? This is what I got from $.client.profile() on Jon's phone which runs Android 4.04:

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2012-07-02 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 James Forrester jforres...@wikimedia.org changed: What|Removed |Added Priority|Unprioritized |High

[Bug 38128] VisualEditor should not try to initialise if no ContentEditable support

2012-07-02 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=38128 --- Comment #2 from Brion Vibber br...@wikimedia.org 2012-07-02 23:25:26 UTC --- According to http://stackoverflow.com/questions/1882205/how-do-i-detect-support-for-contenteditable-via-javascript you can check for the contentEditable property