Selection of text is offset and incorrect

NEW
Unassigned

Status

()

Core
Selection
3 years ago
24 days ago

People

(Reporter: Ray Satiro, Unassigned)

Tracking

({parity-chrome, testcase})

Trunk
parity-chrome, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

3 years ago
Created attachment 8625082 [details]
Selection of text is offset.gif

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20150618030206

Steps to reproduce:

Go to http://www.mediafire.com/developers/core_api/1.3/upload/
In the code window attempt to select some code.


Actual results:

Tested ESR31, Aurora, Nightly: The selection of text is offset and is not what I tried to select. The text should start to select at the location of the mouse pointer but instead starts lines below. I have attached an animated GIF that shows the problem.


Expected results:

The text I select is what should be selected of course. Google Chrome also has some problem with selecting the text in that code box but is more accurate. I could not get the page to load in IE.

Updated

3 years ago
Component: Untriaged → Selection
Product: Firefox → Core

Comment 1

3 years ago
Doesn't work with the old FF8.

Comment 2

3 years ago
Created attachment 8625114 [details]
testcase

css padding and margin causes the problem

Updated

3 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

3 years ago
Whiteboard: [parity-chrome]

Updated

3 years ago
Version: 41 Branch → Trunk

Comment 3

3 years ago
As expected REPRODUCIBLE with DE SeaMonkey 2.35(γ)  (Windows NT 6.1; WOW64; rv:38.0 nightly by Adrian Kalla)  Gecko/20100101 Build 20150615204754 (Classic Theme) on German WIN7 64bit at <http://www.mediafire.com/developers/core_api/1.3/upload/>

Updated

3 years ago
Keywords: testcase
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome
Whiteboard: [parity-chrome]
You need to log in before you can comment on or make changes to this bug.