Weird behavior while selecting table cells with Ctrl and doubleclick

NEW
Unassigned

Status

()

Core
Selection
3 years ago
3 years ago

People

(Reporter: obrufau, Unassigned)

Tracking

33 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:33.0) Gecko/20100101 Firefox/33.0 (Beta/Release)
Build ID: 20140705030203

Steps to reproduce:

Go to a page with a table (e.g. http://ftp.mozilla.org/pub/).

Now press Ctrl key, and keep it pressed during each case.

Case 1:
1. Doubleclick a cell A
        Selected cells: A
        Selected text: A
2. Click some other cells B1, ..., Bk (different than A)
        Selected cells: A, B1, ..., Bk
        Selected text: A
3. Click cell A again
        Selected cells: A, B1, ..., Bk
        Selected text: none
4. Click any cell C (can be A or Bi)
        Selected cells: C
        Selected text: none

Case 2:
1. Click a cell A
        Selected cells: A
        Selected text: none
2. Doubleclick another cell B (different than A)
        Selected cells: A, B
        Selected text: B
3. Click cell B
        Selected cells: A, B
        Selected text: none
4. Click cell B again
        Selected cells: A, B
        Selected text: none


Actual results:

In case 1, clicking a cell selects it (even if it's already selected) and unselects all other cells.

In case 2, you can't unselect cell B by clicking it.


Expected results:

That shouldn't happen.

And maybe double clicking a cell shouldn't select its text.

Updated

3 years ago
Component: Untriaged → Selection
Product: Firefox → Core
Confirmed 33.0a1 (2014-07-14), win 7 x64
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

3 years ago
Dup. of bug 1035036?
(Reporter)

Comment 3

3 years ago
(In reply to Takanori MATSUURA from comment #2)
> Dup. of bug 1035036?

Bug 1035036 is about clicking links in tables, and doesn't seem to cover double click.

This bug doesn't need links, it can be reproduced with text cells too.
You need to log in before you can comment on or make changes to this bug.