ealtenhof@ - Thanks for filing the issue...!!

Tried testing the issue on Win-10 using latest chrome version #62.0.3187.0 by navigating to URL: https://ddm.google.com/ds/cm/cm#all_advertisers.ay=20100000000000895. But it seems that i doesn't have access to the URL and visiting the URL: https://www.google.com/url?q=https://screencast.googleplex.com/cast/NDg3MzU0NTk4MTEwMDAzMnw2NjMwMTIzMi03Yg&sa=D&usg=AFQjCNG8tt8qlD7DpTLFBV1w-PgdaP7-Zg to check the screen cast also lead to an "Uber proxy" error.

Could you please provide any other sample url to triage the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!

Hi,

Are you able to access our development app? I've updated https://buganizer.corp.google.com/issues/64723420 with a link to a reproduction in our development environment and included credentials for logging in.

Thanks!

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

In-house team unable to access the provided development URL, getting "Uber proxy" error page and "We are sorry, but you do not have access to this service" error page is displaying.hence adding the respective label for it to  triage further.

Thank You!

Hi!

After more investigation I believe that this issue is a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=745928

See the discussion in https://groups.google.com/a/google.com/d/msg/gwt-users/LQ45Ui7vhrE/mQdKf9YzBwAJ

We are going to get a fix through the GWT team or a recalculation of absoluteTop on our own end.

Thanks!

Closing as duplicate based on #6

I believe that this issue is the underlying cause of various issues our Chrome users are experiencing related to absolutely positioned elements. It would be very helpful to have access to further details, though. Would it be possible to expand the visibility of bug 745928 to a wider audience so that we can follow that discussion?

Alternatively, could someone share an update on the status of this issue, and/or whether it was decided whether to fix it on the Chromium side or the GWT side?

The issue I reported was fixed on the GWT side. The takeaway I believe was that Chromium was becoming more consistent with other browsers and the issue was in GWT's handling.

Thank you for sharing that update.