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

Issue 711314 link

Starred by 0 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Feature

Blocked on:
issue 708955
issue 751534



Sign in to add a comment

Happy Birthday Doodle is not displayed in NewTabPage

Project Member Reported by srikanthg@chromium.org, Apr 13 2017

Issue description

App Version: 58.0.3029.66 beta
iOS Version: 10.3.2, 10.3
Device: iPhone7, iPhone6 plus, iPad
URL NA

Precondition: Goto https://aboutme.google.com with any testaccount, Edit Birth day to today

Steps to reproduce:
  1. Launch Google Chrome
  2. Sign in with test account for which Birthday is changed to today
  3. Open a new tab

Observed results: Happy Birthday doodle should be displayed

Note: Birthday Doodle is displayed on Mac Chrome NTP, www.google.com if the account signed in.

Expected results: Happy Birthday doodle not displayed. Google Logo is only displayed

Number of times you were able to reproduce: 5/5
Bug reproducible after clean install: Yes
Bug reproducible after clearing cache and cookies: Yes
Bug reproducible on Chrome Mobile on Android: Not Tested
Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA
Bug reproducible on current stable build (App Version, iOS Version): M57 Yes
Bug reproducible on the current beta channel build (App Version, iOS Version): M58 Yes
 

Comment 1 by treib@chromium.org, Apr 13 2017

Has this ever worked? AFAIK, birthday doodles were never implemented on mobile (Android or iOS), though I might be wrong.
Yes, It atleast worked until M44 :)
I was going through an old bug http://crbug/490718. Watch the video from the other bug.

Comment 3 by treib@chromium.org, Apr 13 2017

Hm. Is that when iOS Chrome switched from UIWebView to WKWebView?
M48 is when Chrome switched to WKWebView.

Comment 5 by treib@chromium.org, Apr 13 2017

So, is it possible that birthday doodles broke at that point?

With WKWV, the doodle request does not contain Google signin cookies anymore, so no birthday doodles. Of course, it might have broken even before that, but I guess that doesn't really matter anymore.
Cc: -justincohen@chromium.org rohitrao@chromium.org
Owner: justincohen@chromium.org
Status: Assigned (was: Untriaged)
Cc: treib@chromium.org
treib@ would you like to take this on as part of the new doodle code?

Comment 8 by treib@chromium.org, Apr 13 2017

The new Doodle code will probably support this eventually, but not at first. There will also be server-side changes required to support OAuth2 rather than cookies. Shouldn't be too bad though.
Cc: -treib@chromium.org justincohen@chromium.org
Labels: -Pri-2 Pri-3
Owner: treib@chromium.org
It's not worth doing this work for the current doodle front and backend.  Flipping to treib@ for future work.  Not critical.

Comment 10 by treib@chromium.org, Apr 25 2017

Blockedon: 708955

Comment 11 by treib@chromium.org, Oct 13 2017

Cc: treib@chromium.org
Owner: ----
Status: Available (was: Assigned)
Throwing back into the pool since I don't have concrete plans to work on this.
Project Member

Comment 12 by sheriffbot@chromium.org, Oct 15

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Type-Bug Type-Feature
Status: Available (was: Untriaged)
I think this is still relevant, though really a low-prio feature request rather than a bug.
Cc: ramyan@chromium.org kmilka@chromium.org
+Kyle FYI

FWIW, I cannot set a birthday on a pre-existing account via https://aboutme.google.com.
You can edit it at https://myaccount.google.com/birthday

Just to be clear, the issue here is making the Doodle request authenticated, then the API should automatically do the right thing. Currently we use cookies for authentication, which works on Android and desktop, but not on iOS because there Chrome doesn't actually have access to the content-area cookies.
The solution is probably migrating this all to OAuth2 instead of cookies, which I never got around to.
Labels: NTPDoodle
Thanks! 
Blockedon: 751534

Sign in to add a comment