New issue
Advanced search Search tips

Issue 674951 link

Starred by 1 user
Status: Duplicate
Merged: issue 626581
Owner: ----
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

disabled and readonly properties for textarea elements are not working more

Reported by dcarr...@bankvision.com.co, Dec 16 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Open the test site http://www.w3schools.com/TAgs/tryit.asp?filename=tryhtml_textarea_readonly.
2. As you can see the element textarea has the property readonly also you can add a disabled property.
3. The interpretation of this element with this property should be shown on the right side.

What is the expected behavior?
The element with these properties should not allow the highlight or  and copy of text that has the element inside as the element entries. 

What went wrong?
This behavior should not allow underlining and copying of text from these elements as other browsers. This worked in earlier versions of google.

Did this work before? Yes 55.0.2883.75 or 54.0.2840.99

Does this work in other browsers? Yes

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0

Thanks for your attention please thi is so important to mantain the security of some contents from the web page

Comment 1 by phistuck@chromium.org, Dec 16 2016

Mergedinto: 626581
Status: Duplicate (was: Unconfirmed)
This is unfortunate - you stumbled across a bug fix (or a feature, depending on how you look at it) that was reverted after a single release.
This is the original bug fix or change request -  issue 626581 .
This is the opposite issue to your issue that caused the change to be reverted -  issue 656736 .

Note that there is a disagreement between the browsers. The specification does not define this behavior, so you were relying on undefined and non-interoperable behavior as it is (what if Internet Explorer users visited your website? They could also select and copy data, I believe).

If you do not want users to select and copy your data, there are other ways to do that. Off the top my head, using pointer-events: none in CSS would probably do that (at least partially). Also, using JavaScript, of course.

Since this issue is the same request/bug as  issue 626581 , I am marking this as a duplicate.
►

Sign in to add a comment