New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 734195 link

Starred by 3 users

Issue metadata

Status: Duplicate
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

[Blackberry Hub app]Compose/Reply to email - Typed text does not show up in the body of the email

Project Member Reported by ppolise...@chromium.org, Jun 16 2017

Issue description

This bug was reported by an User in the Webview Beta Channel forum. Here's the link : https://plus.sandbox.google.com/u/0/communities/105434725573080290360?cfem=1

Device name: Samsung Galaxy S7/NRD90M, HTC One(M9)/MRA58K, Nexus6/MOB31T
Monochrome/Webview version : 60.0.3112.33
Application: Blackberry Hub
Application version: 1.5.2.12874
Package: com.blackberry.hub

Precondition: Install Blackberry Hub+ Services

Steps to reproduce:
(1) Install & launch the app
(2) Setup an account with any valid credentials(Ex: gmail account)
(3) In the home screen, tap on Compose icon to compose an email
(4) Input 'To:', 'Subject' fields
(5) Tap on Body of the email and start typing and observe

Expected result: user is able to enter text in the body of the email


Actual result:
(4) Able to input text in 'To:', 'Subject' fields.
(5) Typed text does not show up in the body of the email, the body of the email is blank

Frequency: 5/5

Additional Info:
(1) Issue is also reproducible when replying to an email- nothing gets typed in the body of the email.
(2) Issue is not reproducible with Monochrome/Webview: 58.0.3029.83 & 59.0.3071.92 on the above devices.

Note: I will add logs/bisect info asap.



 

Comment 1 by torne@chromium.org, Jun 16 2017

Labels: -Restrict-View-Google
Please don't file restricted bugs about user bugreports - it means we can't refer the user to the bug. Only restrict bugs if it's absolutely necessary to mention confidential info.
Cc: aelias@chromium.org changwan@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision
This is a regression issue broken in M-60

Per-Version bisect information:
Good build: 60.0.3080.0
Bad build: 60.0.3081.0

Bisect Range:https://chromium.googlesource.com/chromium/src/+log/60.0.3080.0..60.0.3081.0?pretty=fuller&n=10000

Per-CL bisect information:
Good commit:466876
Bad commit:466877

Suspect CL: https://chromium.googlesource.com/chromium/src/+/414a9028af64f0e8d7289b16e829d782f4591368

Logs @ http://go/chrome-androidlogs1/7/734195
Owner: jinsuk...@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by aelias@chromium.org, Jun 16 2017

Labels: ReleaseBlock-Stable
Mergedinto: 715918
Status: Duplicate (was: Assigned)
I think this was also resolved by https://crrev.com/c/532479/ which landed at 61.0.3130.3 Let me dup it. Feel free to reopen it if the problem persists.
Fix verified on Samsung Galaxy S7/NRD90M, Monochrome: 61.0.3136.3.

We will also check the fix on latest Monochrome: M60 and update here. 
Fix verified on Samsung Galaxy S7/NRD90M, Monochrome: 60.0.3112.40.
 Issue 735777  has been merged into this issue.

Sign in to add a comment