New issue
Advanced search Search tips

Issue 837546 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression

Blocked on:
issue 845329



Sign in to add a comment

Regression : Unable to change writing direction of 'Filter' textbox in devtools.

Reported by pranjali...@etouch.net, Apr 27 2018

Issue description

Chrome version : 68.0.3409.2 (Official Build) 90be5dc831f2b7af69690d3b7fa73031c9cdc4c3-refs/branch-heads/3409@{#5}(32/64 bit)

OS : Mac(10.12.6,10.13.1,10.13.5),Windows(7,8,8.1,10) and Linux(14.04 LTS) OS.

Steps to reproduce:
1.Launch Chrome and open devtools on NTP.
2.Go Console section,right click on filter textbox and change writing direction via 
3.Observe.

Actual Result : Unable to change writing direction of 'Filter' textbox in element section of devtools. 
Expected Result : Should be able to change writing direction of 'filter' textbox in element section of devtools. 

This is a regression issue broken in ‘M-63’ and using the per-revision bisect providing the bisect results,
Good build: 63.0.3323.0 (Revision : 503965)
Bad build: 63.0.3325.0  (Revision : 504540)

You are probably looking for a change made after 504147 (known good), but no later than 504148 (first known bad).
CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/b0d454706e1003638749bebb2b397f99b113fd80..a57d5aa65194cc780ab7039d97aa33d11c6d6585

Suspect: https://chromium.googlesource.com/chromium/src/+/a57d5aa65194cc780ab7039d97aa33d11c6d6585

@luoe: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Thank you.
 
Actual_result.mp4
725 KB View Download
Expected_result.mp4
680 KB View Download

Comment 1 by l...@chromium.org, Apr 27 2018

Labels: -Pri-1 Pri-2
Thanks for the report and bisect.  The correct fix is to make all TextPrompts, before and after M63, respect RTL writing direction.

Comment 2 by l...@chromium.org, May 22 2018

Blockedon: 845329

Comment 3 by l...@chromium.org, Jun 28 2018

Status: WontFix (was: Assigned)
Closing, since this is a bug underlying all contentEditable fields.  The other options for DevTools are to switch back to <input>, which is too drastic of a change and not a major priority.

Sign in to add a comment