twitter.com - see bug description

[stefanjudis]

URL: https://twitter.com

Browser / Version: Firefox 113.0
Operating System: Mac OS X 10.15
Tested Another Browser: Yes Chrome

Problem type: Something else
Description: Selection of text behaves differently across browsers
Steps to Reproduce:
Go to Twitter and try to tweet. Before you tweet select some text in the contenteditable text box.

In chrome ::selection is not visible whereas in Safari and Firefox it is.

Here's also a reproducible example outside the Twitter UI.

View the screenshot

Browser Configuration

• None

From webcompat.com with ❤️

[simevidas]

In which version of Chrome did you test? I don’t get the issue in Chrome stable, but I do get it in Canary.

[stefanjudis]

Chrome Version 114.0.5735.106 but funnily, it turns out that turning off experimental web features in Chrome makes it behave similar to Firefox and Safari.

[simevidas]

Yes, Chrome is changing how ::selection works. The new behavior is still experimental.

https://twitter.com/dazabani/status/1440554625501782024

[stefanjudis]

@simevidas are you sure this is still valid? It's 2y old. 😅

[simevidas]

Two years is nothing. There are probably dozens of experimental and unfinished features in browsers that are older than that.

[sv-calin]

We appreciate your report but I was not able to reproduce this issue.

Tested on:
• Browser / Version: Firefox Release 114.0.1 / Chrome Version 114.0.5735.133
• Operating System: Mac OS X 10.15

Suggestions:
• Update the browser to the latest version
• Clear cache/data/cookies, disable Ad-blocker (if available), or use a clean profile and check again
• If there are any changes made to the default settings of the browser (e.g. in about:config), please revert to the default settings

Creating a new profile:

1. Open a new tab and type in the address bar "about:profiles".
2. Click "Create a New Profile".
3. Click "Continue", name your profile and then Click "Done".
4. Head to your newly created profile and click "Launch profile in new browser".

[qa_24/2023]

[stefanjudis]

@sv-calin Thanks for investigating. Sorry forget to close.

Yes, the compact issue is behind chrome's experimental flags as stated above.

Chrome Version 114.0.5735.106 but funnily, it turns out that turning off experimental web features in Chrome makes it behave similar to Firefox and Safari.

I'll close here. :)