Open Bug 1427430 Opened 8 years ago Updated 2 years ago

Double-click on number should select whole number (including decimals), as well as provide Search/Copy actions

Categories

(Core :: DOM: Selection, defect, P3)

Product:
Core
Component:
DOM: Selection
Version:
57 Branch
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: tranvanthien2002, Unassigned)

References

Details

(Keywords: polish)

Attachments

(1 file)

Snap19.jpg
28.00 KB, image/jpeg
Details
Attached image Snap19.jpg —
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 OPR/49.0.2725.64 Steps to reproduce: Dear develop could you fix a small issue when double click on decimal number it can't copy all number as like as opera browser did. for example. when double click on 123.4567 it only copy 123 or 4567 . not 123.4567. i want it copy full number. please see the picture. Actual results: as mention above Expected results: as mention above
and 1 more suggestion. when double click on any text or number it show Search\Copy text box as like as opera browser did. that is very useful. please see the picture attached. thank you very much.
Component: Untriaged → Editor
Keywords: polish
Product: Firefox → Core
Summary: A suggestion. firefox quantum 57.0.3 64bit → Double-click on text behaviors
thank you for your attention . hope you fix it asap.
Component: Editor → Selection
Summary: Double-click on text behaviors → Double-click on number should select whole number (including decimals), as well as provide copy / copy actions
Search/Copy actions.
Summary: Double-click on number should select whole number (including decimals), as well as provide copy / copy actions → Double-click on number should select whole number (including decimals), as well as provide Search/Copy actions
thank you for your attention. when will you add those features ?
[ Triage 2017/02/20: P3 ]
Priority: -- → P3
Severity: normal → S3

As far as I can tell, the actual results in this case is the platform behavior in GTK. The original reporter in this case is on macOS, which has the expected behavior in the native text editor (TextEdit). I haven't tested Windows, but if this bug gets picked up, it likely makes sense to match the native behavior.

WebKit and Chromium on Linux also seems to have the "actual" behavior (rather than the native one) - which seems undesirable to me.

Also marking bug 393227 as see also as it reports a similar looking issue.

See Also: → 393227

(In reply to Asif Youssuff from comment #6)

As far as I can tell, the actual results in this case is the platform behavior in GTK. The original reporter in this case is on macOS, which has the expected behavior in the native text editor (TextEdit). I haven't tested Windows, but if this bug gets picked up, it likely makes sense to match the native behavior.

The same happens in Windows 11. Also see https://www.reddit.com/r/FirefoxCSS/comments/1ag7m0h/the_default_behaviour_of_firefox_where_like_2686/.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: