780174 - [browser] Cannot scroll disabled textareas

Status: RESOLVED DUPLICATE of bug 817845

(Firefox OS Graveyard :: General, defect)

Description

[Justin Lebar (not reading bugmail)]

+++ This bug was initially created as a clone of Bug 773356 +++

Bug 773356 fixes scrolling in enabled textareas in B2G.  But disabled textareas still do not scroll.

STR:
1. launch browser app
2. go to http://people.mozilla.com/~nhirata/html_tp/disabled_textarea%20no%20scroll.html
3. try to scroll in the disabled field using your finger if you're on the device, or click-and-drag if you're on desktop.

Expected:
* you can scroll

Actual:
* can't scroll

From : https://github.com/mozilla-b2g/gaia/issues/2311#issuecomment-6933190

See bug 773356 for discussion about this issue.

Comment 1

[Justin Lebar (not reading bugmail)]

Resetting blocking to ?.  This is not as bad as bug 773356, because you can now scroll enabled textareas.

If we decide this blocks, we need to find resources to fix it.  At the moment, we don't have anyone capable and able to work on this bug.

Comment 2

[Andrew Overholt [:overholt]]

There's a risk for ex. sites with EULAs marked read only ...

Comment 3

[Boris Zbarsky [:bzbarsky]]

Readonly and disabled are not the same thing for textareas.  Do sites use the former or the latter?

Comment 4

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

We don't know. Presumably there are sites that use readonly and sites that use disabled. At least assuming both are scrollable in desktop firefox.

Comment 5

[Mounir Lamouri (:mounir)]

All browsers I have been able to test make readonly textareas more readable than disabled textareas (which are barely readable). I hope web developers got the hint that when the text has to be read, readonly should be used... (they can still style those so...)

Comment 6

[mlevin]

The issue persist on Unagi build 20130104070203. 

Cannot scroll within one of the fields at http://people.mozilla.com/~nhirata/html_tp/formsninput.html after typing in a large amount of text, then going to another field, then going back to the original field.

Comment 7

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

That test case wfm.  That was bug 817845.

In the test in comment 0, I can scroll the enabled input but still can't scroll the disabled one.

Comment 8

[Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz)]

I cannot reproduce this bug on my otoro with today's m-c and b2g18 codebase, mark as a dup of bug 817845.