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

Issue 663863 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug



Sign in to add a comment

Awkward behavior with Physical Web in Chrome Today View widget

Project Member Reported by animohan@chromium.org, Nov 9 2016

Issue description

Version: 54.0.2840.91 (Stable)
OS: iOS 10.0

What steps will reproduce the problem?
(1) Add the Chrome Today View widget. 
(2) Go near a Physical Web beacon broadcasting a URL.
(3) Look at the widget. Results appear cut off. 

What is the expected result?
You should see the full list of nearby URLs (and when opting in, the full opt-in message).

What happens instead?
Results appear cut off. The only way to see the full list is to toggle the 'Show More' button on the widget, but this does not reliably toggle.

See these screenshots for what currently happens:

Opt-in dialog: go/pw-today-opt-in
Result listing 1: go/pw-today-result-1
Result listing 2: go/pw-today-result-2

Please use labels and text to provide additional information.

 
Looks like the go-links don't work for the screenshots. Here's an album with the screenshots I see: https://goo.gl/photos/5ddjvTffccmRvw7i8
Status: Assigned (was: Untriaged)

Comment 3 by scottj@google.com, Nov 30 2016

We're getting comments on our Physical Web mailing list complaining about this. Is there any news on this? Hopefully a fix is coming?
Labels: ReleaseBlock-Stable M-56
I will check this tomorrow

Comment 5 by scottj@google.com, Dec 2 2016

Any chance we can get an update before the weekend?
This will be hard.
I checked the code and the resize method is correctly called. 
I am not sure why the widget is not resized.
The bug seems to happen when you press the button too early after it is displayed.
Status: Started (was: Assigned)
I will do a tentative fix based on the SO solution so we can test on canary.
Project Member

Comment 10 by bugdroid1@chromium.org, Dec 2 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/79e2f29010f9dbb42450766d2e1714162a40b17b

commit 79e2f29010f9dbb42450766d2e1714162a40b17b
Author: olivierrobin <olivierrobin@google.com>
Date: Fri Dec 02 17:04:42 2016

Submitted a CL. Can you test canary on Monday? If this is fixed, I will cherry-pick to 56.
Great! Thanks so much for chasing this down. Happy to test on Monday.
Project Member

Comment 13 by bugdroid1@chromium.org, Dec 5 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/419b2729f89c05d2b2e29b8ff61bf5a0a56f5314

commit 419b2729f89c05d2b2e29b8ff61bf5a0a56f5314
Author: olivierrobin <olivierrobin@google.com>
Date: Mon Dec 05 12:13:36 2016

I tried this with the latest Canary build (57.0.2939.0 Canary), not sure if it had your changes in it yet but the widget still doesn't expand reliably for me. I'll try again tomorrow.
The canary has my change.
I tested it and did not see issue.
When you upgrade, can you ensure that Springboard is reloaded (either reboot the phone or change phone language).
Do you have multiple Chrome widgets (interactions may cause problems)
Do you have more than 3 beacons visible and should the resize be bigger than the screen?

Thanks for these elements.
I recorded a video showing the bug on my device (iPhone 6s, iOS 10.1):

https://drive.google.com/a/google.com/file/d/0B9RNNlGSHjA9bE5WNVh3bHdXM0k/view?usp=sharing

This was recorded just after rebooting, and I've disabled all other Chrome widgets. There are ~5 beacons nearby, though I still see the bug even in onboarding mode so the number of beacons probably isn't relevant.
OK, problem arise when you dismiss/reopen the widget in expanded mode.
I will try to see what happens in that scenario
I made some more tests, and I have a very speculative fix.
This should be in canary tomorrow, if you can test.

Project Member

Comment 19 by bugdroid1@chromium.org, Dec 7 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/c127cae7cb7efe5a66cee369fb00b80dbe4d80c8

commit c127cae7cb7efe5a66cee369fb00b80dbe4d80c8
Author: olivierrobin <olivierrobin@google.com>
Date: Wed Dec 07 18:36:02 2016

Project Member

Comment 20 by bugdroid1@chromium.org, Dec 7 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/c127cae7cb7efe5a66cee369fb00b80dbe4d80c8

commit c127cae7cb7efe5a66cee369fb00b80dbe4d80c8
Author: olivierrobin <olivierrobin@google.com>
Date: Wed Dec 07 18:36:02 2016

I tested again with Olivier's change that just landed ("Constrain the size of the NC widget"). I couldn't repro the Show More/Less bug anymore, but I'm seeing a different bug where the contents of the widget fail to render:

https://drive.google.com/open?id=0B9RNNlGSHjA9ZldQemVUTl9OY1U

This seems to happen more frequently if I expand the widget and then quickly swipe back to the home screen, then back to the Today view.
Status: Fixed (was: Started)
I propose to close this bug So I can request for merge on this.
I cannot reproduce consistently the not rendering issue, but I will investigate more.
Please tell me if you have reliable reproduction steps.
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-56; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-56 label, otherwise remove Merge-TBD label. Thanks.
Labels: -Merge-TBD Merge-Request-56

Comment 25 by dimu@chromium.org, Dec 8 2016

Labels: -Merge-Request-56 Merge-Approved-56 Hotlist-Merge-Approved
Your change meets the bar and is auto-approved for M56 (branch: 2924)

Comment 26 by s...@google.com, Dec 10 2016

You tried to cherry pick this by passing "-a 56.0.2924":
https://uberchromegw.corp.google.com/i/internal.bling.tryserver/builders/beta-cherry-picker/builds/1012

You need to pass "-a 2924" instead.
Yes, I noticed that. But as I have 3 CL to cherry-pick, I decided to postpone to Monday.
BTW, it would be useful to be able to specify multiple CLs to the cherry-picker.
Project Member

Comment 28 by bugdroid1@chromium.org, Dec 12 2016

Labels: -merge-approved-56 Merge-Merged-2924
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/a2a9049af6b7ccf72cf8576b993820e4f98b0190

commit a2a9049af6b7ccf72cf8576b993820e4f98b0190
Author: olivierrobin <olivierrobin@google.com>
Date: Fri Dec 02 17:04:42 2016

Project Member

Comment 29 by bugdroid1@chromium.org, Dec 12 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/806ea6f6b0822ea47498be209ed10e09e7435ae0

commit 806ea6f6b0822ea47498be209ed10e09e7435ae0
Author: olivierrobin <olivierrobin@google.com>
Date: Mon Dec 05 12:13:36 2016

Project Member

Comment 30 by bugdroid1@chromium.org, Dec 12 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/768cae66c7dc68cdf7e1a5261b95164df46c49f0

commit 768cae66c7dc68cdf7e1a5261b95164df46c49f0
Author: olivierrobin <olivierrobin@google.com>
Date: Wed Dec 07 18:36:02 2016

Comment 31 Deleted

Verified on clean install on 57.0.2950.0 canary iPhone6Plus iOs 10.2, iPhone6 iOS 10.0.3. Looks good.Results are not cut off.
Verified on a clean install of build 56.0.2924.28 beta on iPhone6Plus  iOS 10.2, iPhone7 iOs 10.0.3
Looks good.Results are not cut off.Tapping On tapping "Show More" drops down the list of beacons available and also the "Show More Results" text. 
Project Member

Comment 34 by sheriffbot@chromium.org, Dec 16 2016

Labels: Merge-Review-56 Hotlist-Merge-Review
This bug requires manual review: No test file found in commits.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 35 by sheriffbot@chromium.org, Dec 16 2016

This bug requires manual review: No test file found in commits.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Hotlist-Merge-Review -Hotlist-Merge-Approved -Merge-Review-56
Status: Assigned (was: Verified)
Current behavior on build 56.0.2924.73 dev on iPhone 6+ iOS 10.2.1
https://drive.google.com/open?id=0B6GVWQnhaMClbXpHNmF6c0R1STg

Labels: -M-56 M-57
Status: Fixed (was: Assigned)
Fix is in M-57.
Some parts were not cherry-picked to M-56.
Status: Verified (was: Fixed)
https://drive.google.com/open?id=0B6GVWQnhaMClXzBidV9rRTI1dDA
Verified on build 57.0.2987.83 dev on iPhone 6+ iOS 10.2.1 , iPad Pro iOS 10.2.1 .
The copied link is present.Hence the  full list of nearby URLs can be seen only if "Show More" is tapped on.

Sign in to add a comment