I believe fading was removed when we added support for theme colors.  We have to draw the fade ourselves instead of relying on Android and the composed colors of theme colors makes that difficult.

Adding UX and PM to discuss further though.

+emily from omnibox team

I'm open to using the fading behavior of iOS. Is it a significant amount of work to make it fade?

UX agreeing - like ktam@ it's fine with me to match iOS if it doesn't cause any performance problems and it's not a hassle to implement.

It would be great for Android to match iOS! It's important that the eTLD+1 is preserved -- iOS does this correctly - see slide 3 here (https://docs.google.com/presentation/d/1OVXsjFm5DqzxnK97klcJ-qfeBB_nI1DloK9fEoHanGc/edit#slide=id.g15cb312756_0_117)

Not directly related to this URL fading feature, but there is another small feature that is in Chrome for Android phones but not Chrome for iPhone, and I cannot fathom why other than the Chrome for iPhone team and Chrome for Android phones team are separate and not communicating well... I'll report it but the root of the problem is, there should be 1 unified "Chrome for Phones" team (I understand there is significant differences between Android and the iPhone, but still), but at the moment it really seems like there is a Chrome for iPhone team and also a Chrome for Android phones team and they aren't communicating well. A website wrote an article recently stating how strangely, Google's iPhone apps are in some ways better than Google's Android apps! If anything, it should be the other way around! 

here is the other small missing feature for those interested https://bugs.chromium.org/p/chromium/issues/detail?id=679083 I just filed it

Well if theme colors is preventing the fading from happening, it can still be done in incognito mode because the incognito bar color is always the same 

Just thought I should mention that Firefox for Android fades out too 

posting this here because it's very very similar, if not the same https://bugs.chromium.org/p/chromium/issues/detail?id=688867 

Issue 688867 has been merged into this issue.

maxwalker@ to be the design person on this

Is this being worked on? The URL bar is visible such a large amount of the time, it really should fade out. I really do think of this as something important, it's not about prettiness, it's functional

Adding pschaffner@ and srahim@ who are working on a Chrome standard for truncation.

I think this should be a higher priority because it's so highly visible. And since Chrome Home no longer has theme colors, could this be re-enabled just for Chrome Home?

It's a visible surface, but we have only a couple of people to work on hundreds of bugs in that visible surface, and many of them are more immediately critical than this one.

Please don't forget this!

Bumping in case this was forgotten :) 

The clipping can occur on the left and right in the steady- and edit state, see attachment for examples.

Ted, could you comment on technical feasibility? Any performance considerations? If fading isn't feasible for theme colors, would limiting it to regular and incognito toolbars be an option? (A solution that works everywhere would be preferable of course.)

Adding Hannah for Clank visual design.

Deleted: Clipped vs Fade.png 403 KB

	Clipped vs Fade.png 403 KB View Download

+twellington +mdjones

If we have a reliable way to calculate the computed color of the text box w/ transparency and the underlying color (ColorUtils#getColorWithOverlay perchance), then we should be able to do it for all variants of the toolbar.

The main complexity at this point would be the focusing/unfocusing animation.  We need to animate the clipped area as we are doing the transition.

We are looking at rewriting a bunch of that logic though, so we might be able to add this in as a feature enhancement along the way.