Not a P0, dropping to P2. This looks like it is an issue for facebook itself as hint text is just a div they hide.

Did you do a bisect to see if it is actually caused a change Chromium made?

Tested the issue in Android and could reproduce the issue.

Steps Followed:
1. Launched Browser
2. Navigated to news article which can be shared via FB
3. Clicked on Share, logged into FB, close the tab
4. Again tried sharing the news artcile
5. observed close button, maps button are not clickable

Chrome versions tested:
61.0.3163.98, 62.0.3202.52

OS
Android 6.0.1

Android Devices
6.0.1: SM-J710F Build/MMB29K

Below is the bisect info
=======================

Chrome Good Build -- 61.0.3162.0, 61.0.3163.0 
Chrome Bad Build  -- 61.0.3163.98

https://chromium.googlesource.com/chromium/src/+log/61.0.3162.0..61.0.3163.0?pretty=fuller&n=10000

Invoked all good builds in in per revision bisect.

Unable to find the suspect from above range, someone from dev team look in to this issue.

Note: Issue is not observed in latest Dev #63.0.3236.6 and Canary #64.0.3242.0 as well.

Please navigate to below link for log's and video--
go/chrome-androidlogs/774978


Thanks!!

Assigning to the concern owner who might be related --
@fmalita --Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

It's hard to pinpoint the area at this stage (input? inval? layout?), and I am not a good owner unless we can narrow it down to a paint/rasterization issue.

Is it possible to run a more granular bisect?  The range is too coarse to be useful.  If not, I would suggest assigning to someone on the Android Chrome team for further triage/investigation (aelias@?).

I am unable to reproduce in my environment. I agree with fmalita that while I can clearly see you're experiencing the problem, without a clear local repro or a reduction, the issue is not actionable.

It is also unclear to me whether this is a Chrome/Blink issue, or just a spurios failure of the FB front-end.

The NextAction date has arrived: 2017-10-27

Sandeep, please re-bisect.

Tried reverse bisect for the issue and got all bad builds invoked.

Reverse bisect result:
You are looking for a change made after 488527(BAD), but before 488528(GOOD).

MANUAl CHANGELOG:
https://chromium.googlesource.com/chromium/src/+log/61.0.3162.0..61.0.3163.0?pretty=fuller&n=10000

Unable to find the suspect from above range.

@fmalita: Could you please help us in assigning this issue to the appropriate owner.

Thanks!!

This needs a more fine grained bisect to proceed, the regression range indicated in comment 11 has almost 500 changes and isn't really actionable.

The changelist above is wrong, I think. I tried bisecting and found the issue to be a little difficult to reproduce and flaky until you get the hang of it. It looks like you have to start typing before the load finishes. Once the page is loaded, the background text will stick around. But if you type more text it disappears. I tried revisions from before the range above and they reproduced as well so I think this may be an issue on Facebook's end (though I didn't go too far back).

I also tried reproducing in Firefox and Safari but it looks like the share page loads much quicker and so the issue didn't repro. Any objections to marking this WontFix? Could we reach out to someone on FB's end and have them take a look?

Actually, scratch that. It seems in stable the background text doesn't disappear even after typing more text. Will take another look...

No longer reproduces in 67.0.3381.2