Closed Bug 814274 Opened 12 years ago Closed 11 years ago

mobile.twitter.com does not allow user to select text while composing a text (because -moz-user-select:none)

Categories

(Web Compatibility :: Site Reports, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cpeterson, Unassigned)

References

()

Details

TL;DR? Twitter should use "-moz-user-select:-moz-none", not "-moz-user-select:none".

STR:
1. With Firefox for Android or desktop, load https://mobile.twitter.com/compose/tweet
2. Enter some text
3. Try to select the text

RESULT:
You cannot select the text or insert new text.

The problem is that mobile.twitter.com's CSS specifies "-moz-user-select:none", which regrettably behaves differently from "-webkit-user-select:none". Twitter should use "-moz-user-select:-moz-none" to get the WebKit-like behavior:

https://developer.mozilla.org/en-US/docs/CSS/user-select
Blocks: 799029
Block twitter.com meta bug 763510
Blocks: twitter.com
Depends on: 816298
Blocks: b2g-twitter
No longer blocks: b2g-twitter
Blocks: b2g-twitter
Fix is ready and will be deployed in the next couple of days.
Summary: mobile.twitter.com does not allow user to select text while composing a text (because -moz-user-select:none) → (Android) mobile.twitter.com does not allow user to select text while composing a text (because -moz-user-select:none)
The title change here is incorrect. See one of the dupes here - this affects all platforms.
OS: Android → All
Summary: (Android) mobile.twitter.com does not allow user to select text while composing a text (because -moz-user-select:none) → mobile.twitter.com does not allow user to select text while composing a text (because -moz-user-select:none)
Seems this fix is rolled out (tested on desktop) - Karl or Lawrence, could you verify?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
(Or does it just seem fixed to me because a fix for 816298 is in my Firefox 23?)
I see this styling:

.userselect {
    -moz-user-select: text;
}

so it seems RESOLVED FIXED is correct :)
Product: Tech Evangelism → Web Compatibility
Component: Mobile → Site Reports
You need to log in before you can comment on or make changes to this bug.