Fixed

Bug

Status Update

No update yet.

Description

te...@gmail.com

created issue #1

Mar 30, 2021 09:48PM

Describe your issue

Many places in the Google Maps Javascript API client libraries apparently use non-passive event listeners, and this generates warnings in the developer console like this: Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

This can be quite annoying, and in some cases can generate a quite large number of warnings. Apparently, this has been noticed by many other developers, as seen in this stack overflow question with 29 upvotes: Javascript Google Maps API & non-passive event handlers.

As this occurs in Google code, I cannot fix it. In my React based application, this can generate hundreds of console messages, and lock up the application while the developer console logs these messages. It occurs in many places in Google code, and as said code is heavily obfuscated, I'm not able to give you good advice on where the problem is, other than a few snippets, like this function in util.js, which the console message points me to:

    KB = function(a, b) {
        return function(c) {
            var d = a
              , e = b
              , f = !1;
            "mouseenter" == d ? d = "mouseover" : "mouseleave" == d && (d = "mouseout");
            if (c.addEventListener) {
                if ("focus" == d || "blur" == d || "error" == d || "load" == d)
                    f = !0;
                c.addEventListener(d, e, f)
            } else
                c.attachEvent && ("focus" == d ? d = "focusin" : "blur" == d && (d = "focusout"),
                e = pA(c, e),
                c.attachEvent("on" + d, e));
            return {
                De: d,
                Fd: e,
                capture: f
            }
        }
    }
    ;

> google.maps.version

3.44.7

What steps will reproduce the problem? Please also provide a code sample which demonstrates your issue (e.g. via jsfiddle.net, or jsbin.com)

It would be time consuming to produce a minimal repro of this. It affects many developers and is not a complex logic bug, do I really need to?

I have searched known issues, and did not see anything similar.

Comments

rc...@google.com <rc...@google.com> #2Mar 31, 2021 07:19AM

Assigned to rc...@google.com.

Thanks for the post.

Upon checking, it appears that this is a duplicate of https://issuetracker.google.com/63211698, and we may need to re-open that. But before we can proceed to help you further, we would really need a reproducible sample (http://sscce.org) that will demonstrate the issue. We understand that this may be time consuming, but we would really require this to proceed accordingly. You can provide a self contained sample in jsfiddle (http://jsfiddle.net/) which you can then send us the link so that we may take a look at it.

Thank you for your patience and contributions.

te...@gmail.com <te...@gmail.com> #3Apr 1, 2021 05:55AM

Hmm, I don't know how I missed that old bug, I did do a search.

I'm not sure how long it will take me to get a minimal repro working, but I can say that it was really easy to spin up a repor as a minimal react project with the react-google-maps/api component. Doing absolutely nothing but mounting the map generates 16 of these warnings.

I'll see what I can do.

te...@gmail.com <te...@gmail.com> #4Apr 3, 2021 12:39AM

I'm not sure how self contained this is, but I was able to instantiate the "Simple Map" javascript API sample, and add a single line of code to the initMap function: map.addListener("onClick", () => {return;});, and it generates sixteen of these warnings:


20:33:29.243 Navigated to file:///C:/Users/Lucius%20Riccio/Documents/GitHub/react-google-maps-warning-bug/simple_repro/public/index.html
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:31.255 [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
20:33:29.766 util.js:43 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
(anonymous) @ util.js:43
_.GE @ util.js:128
Nga @ onion.js:37
(anonymous) @ onion.js:44
20:33:29.766 util.js:43 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
(anonymous) @ util.js:43
_.GE @ util.js:128
Nga @ onion.js:37
(anonymous) @ onion.js:44
20:33:30.229 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
hO @ controls.js:132
_.n.Nn @ controls.js:193
(anonymous) @ map.js:99
20:33:30.233 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
JN @ controls.js:103
QN @ controls.js:110
ida @ controls.js:138
hO @ controls.js:134
_.n.Nn @ controls.js:193
(anonymous) @ map.js:99
20:33:30.235 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
(anonymous) @ util.js:175
_.xe @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:73
_.CJ @ util.js:175
NN @ controls.js:105
QN @ controls.js:110
ida @ controls.js:138
hO @ controls.js:134
_.n.Nn @ controls.js:193
(anonymous) @ map.js:99
20:33:30.237 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
TM @ controls.js:48
QN @ controls.js:111
ida @ controls.js:138
hO @ controls.js:134
_.n.Nn @ controls.js:193
(anonymous) @ map.js:99
20:33:30.238 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
gO @ controls.js:137
hO @ controls.js:134
_.n.Nn @ controls.js:193
(anonymous) @ map.js:99
20:33:30.259 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
CN @ controls.js:100
FN @ controls.js:98
GN @ controls.js:102
qda @ controls.js:144
fda @ controls.js:148
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241
20:33:30.259 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
CN @ controls.js:100
FN @ controls.js:99
GN @ controls.js:102
qda @ controls.js:144
fda @ controls.js:148
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241
20:33:30.271 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
xN @ controls.js:89
yN @ controls.js:92
sda @ controls.js:145
fda @ controls.js:148
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241
20:33:30.272 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
xN @ controls.js:90
yN @ controls.js:92
sda @ controls.js:145
fda @ controls.js:148
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241
20:33:30.272 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
xN @ controls.js:90
yN @ controls.js:92
sda @ controls.js:145
fda @ controls.js:148
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241
20:33:30.276 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
fN @ controls.js:63
_.gN @ controls.js:67
Rca @ controls.js:81
oN @ controls.js:79
gda @ controls.js:142
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241
20:33:30.276 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
fN @ controls.js:63
_.gN @ controls.js:67
Rca @ controls.js:81
oN @ controls.js:79
gda @ controls.js:142
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241
20:33:30.281 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
_.ME @ util.js:132
fN @ controls.js:63
_.gN @ controls.js:67
Rca @ controls.js:81
oN @ controls.js:79
gda @ controls.js:142
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241
20:33:30.281 util.js:26 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
_.TA @ util.js:26
fN @ controls.js:63
_.gN @ controls.js:67
Rca @ controls.js:81
oN @ controls.js:79
gda @ controls.js:142
(anonymous) @ controls.js:131
_.n.Hi @ js?key=AIzaSyAvf-00kEHOEuEs0pcOmEkGfNnpu_NNnDY&callback=initMap&libraries=&v=weekly:241

I'm attaching it without the node_modules. It shouldn't be needed, I generated these warnings after generating a production build in public. Try running it locally.

simple_repro.7z

101 KB

Download

rc...@google.com <rc...@google.com> #5Apr 3, 2021 12:43AM

Thank you for waiting.

Just to further clarify, one of the main reasons why we are asking for a self contained sample is also to make sure that the issue is with our Maps API, and not with the 3rd party react library that you are using. As we only support the API itself, and 3rd party frameworks/libraries are generally not part of our scope.

We will patiently wait for your response. Thank you!

rc...@google.com <rc...@google.com> #6Apr 3, 2021 12:46AM

Hello,

It seems we have sent our comments only a few minutes apart. That said, thank you for providing that info, we will get back to you as soon as we can or if we need more info. Thank you!

Message last modified on Apr 3, 2021 12:46AM

rc...@google.com <rc...@google.com> #7Apr 6, 2021 04:08AM

Status: Won't Fix (Infeasible)

Thank you for patiently waiting for a response.

Upon inspection, we can see that you are actually using a 3rd party library @types/google.maps to implement Maps API. As mentioned previously, we only support the API itself, and 3rd party frameworks/libraries are not part of our scope. The issue is also not apparent using the samples in our documentation.

So as much as we would like to help you, the best we can do is to point you in this repository here where you can raise the issue.

te...@gmail.com <te...@gmail.com> #8Apr 6, 2021 03:39PM

Fair enough. So, I went back and simplified it to only manually use the raw Google Maps Javascript API in a script tag in a minimal html document. It still reproduces, and triggers 16 passive event listener warnings. I'll attach, please reopen!

minimal.html

907 B

View

Download

te...@gmail.com <te...@gmail.com> #9Apr 6, 2021 03:42PM

Wait a second, it appears that I'm triggering the warning without even adding my own event listener!

minimal.html

910 B

View

Download

rc...@google.com <rc...@google.com> #10Apr 7, 2021 03:13AM

Status: Assigned (reopened)

Thank you for waiting.

We can't seem to replicate the issue with the attachment you sent in jsfiddle. Can you please provide a self-contained sample in jsFiddle to prevent any caching/unnecessary variables? You can send us the link after reproducing the issue.

te...@gmail.com <te...@gmail.com> #11Apr 7, 2021 09:00PM

Well this is certainly curious. If I paste my repro into fiddle and then run it, my browser console also generates the warnings, but nothing shows up in the fiddle console.

This is a funny heisenbug for sure. Now I have no clue why it would generate warnings on my machine but not yours. Let me investigate a bit further.

te...@gmail.com <te...@gmail.com> #12Apr 7, 2021 09:09PM

I get the warnings in incognito mode too, so it's not something to do with extensions. There don't appear to be any chrome flags that might affect this either. My Chrome version string (as copied from about chrome) is: Version 90.0.4430.51 (Official Build) beta (64-bit). Are you trying to reproduce with a different version? Older or newer? Maybe because I'm on the beta channel? Are you looking at verbose messages in console too?

rc...@google.com <rc...@google.com> #13Apr 8, 2021 03:04AM

Status: Won't Fix (Infeasible)

Thank you for waiting.

We tested this on both Windows and Chrome OS with both of their browsers having version 89.0.4389.116 (Official Build) (64-bit). No such warnings was generated in both the JSfiddle and browser's console. Perhaps try it in a different device and see if that helps.

te...@gmail.com <te...@gmail.com> #14Apr 12, 2021 07:56PM

Interesting. We seem to have a true heisenbug here. I will try to repro on other devices, and will update.

Would native stack traces help? I think I can quite easily drop into windbg and give you the exact code that's triggering it.

te...@gmail.com <te...@gmail.com> #15Apr 12, 2021 09:23PM

It's a bit difficult to get a breakpoint on ReportBlockedEvent because it's in an anonymous namespace and is inlined, but it doesn't seem like I'm hitting it anyways. Perhaps that means something?

So the very top of the stack from where some of the warnings are seemingly being generated through ReportGenericViolation is:

Breakpoint 6 hit
chrome!blink::PerformanceMonitor::ReportGenericViolation:
00007fff`02bf9a40 56              push    rsi
0:000> kPa
 # Child-SP          RetAddr           Call Site
00 00000027`cbdfd508 00007fff`05c1615a chrome!blink::PerformanceMonitor::ReportGenericViolation(
			class blink::ExecutionContext * context = 0x0000277d`8cbfba40, 
			blink::PerformanceMonitor::Violation violation = kDiscouragedAPIUse (0n4), 
			class WTF::String * text = 0x00000027`cbdfd570 
        Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952, 
			class base::TimeDelta time = class base::TimeDelta, 
			class std::__1::unique_ptr<blink::SourceLocation,std::default_delete<blink::SourceLocation> > location = <Value unavailable error>) [c:\b\s\w\ir\cache\builder\src\third_party\blink\renderer\core\frame\performance_monitor.cc @ 40] 
01 00000027`cbdfd510 00007fff`05a35461 chrome!blink::EventTarget::SetDefaultAddEventListenerOptions(
			class WTF::AtomicString * event_type = 0x00000027`cbdfd648 
        touchstart, 
			class blink::EventListener * event_listener = <Value unavailable error>, 
			class blink::AddEventListenerOptionsResolved * options = 0x00003ba3`82d30558)+0x23a [c:\b\s\w\ir\cache\builder\src\third_party\blink\renderer\core\dom\events\event_target.cc @ 439] 
02 (Inline Function) --------`-------- chrome!blink::EventListenerOptions::setCapture(
			bool value = <Value unavailable error>)+0x19 [c:\b\s\w\ir\cache\builder\src\out\Release_x64\gen\third_party\blink\renderer\core\dom\events\event_listener_options.h @ 50] 
03 (Inline Function) --------`-------- chrome!blink::EventTarget::addEventListener(
			class WTF::AtomicString * event_type = <Value unavailable error>, 
			class blink::EventListener * listener = <Value unavailable error>, 
			bool use_capture = <Value unavailable error>)+0x54 [c:\b\s\w\ir\cache\builder\src\third_party\blink\renderer\core\dom\events\event_target.cc @ 482] 
04 00000027`cbdfd5c0 00007fff`05a3498b chrome!blink::EventTarget::addEventListener(
			class WTF::AtomicString * event_type = 0x00000027`cbdfd648 
        touchstart, 
			class blink::V8EventListener * listener = <Value unavailable error>, 
			class blink::AddEventListenerOptionsOrBoolean * options_union = <Value unavailable error>)+0x101 [c:\b\s\w\ir\cache\builder\src\third_party\blink\renderer\core\dom\events\event_target.cc @ 455] 
05 00000027`cbdfd620 00007fff`055b86e6 chrome!blink::`anonymous namespace'::AddEventListenerOperationCallback(
			class v8::FunctionCallbackInfo<v8::Value> * info = 0x00000027`cbdfd870)+0x30b [c:\b\s\w\ir\cache\builder\src\out\Release_x64\gen\third_party\blink\renderer\bindings\core\v8\v8_event_target.cc @ 154] 
06 00000027`cbdfd7c0 00007fff`055b819e chrome!v8::internal::FunctionCallbackArguments::Call(
			class v8::internal::CallHandlerInfo handler = <Value unavailable error>)+0x126 [c:\b\s\w\ir\cache\builder\src\v8\src\api\api-arguments-inl.h @ 159] 
07 00000027`cbdfd8f0 00007fff`055b7ede chrome!v8::internal::`anonymous namespace'::HandleApiCallHelper<0>(
			class v8::internal::Isolate * isolate = 0x0000423d`00000000, 
			class v8::internal::Handle<v8::internal::HeapObject> function = <Value unavailable error>, 
			class v8::internal::Handle<v8::internal::HeapObject> new_target = class v8::internal::Handle<v8::internal::HeapObject>, 
			class v8::internal::Handle<v8::internal::FunctionTemplateInfo> fun_data = class v8::internal::Handle<v8::internal::FunctionTemplateInfo>, 
			class v8::internal::Handle<v8::internal::Object> receiver = class v8::internal::Handle<v8::internal::Object>, 
			class v8::internal::BuiltinArguments * args = 0x00000027`cbdfda30)+0x1ee [c:\b\s\w\ir\cache\builder\src\v8\src\builtins\builtins-api.cc @ 115] 
08 00000027`cbdfd9f0 00007fff`055b7d97 chrome!v8::internal::Builtin_Impl_HandleApiCall(
			class v8::internal::BuiltinArguments * args = 0x00000000`00000008, 
			class v8::internal::Isolate * isolate = 0x0000423d`00000000)+0xfe [c:\b\s\w\ir\cache\builder\src\v8\src\builtins\builtins-api.cc @ 143] 
09 00000027`cbdfdab0 00007fff`05f6a87c chrome!v8::internal::Builtin_HandleApiCall(
			int args_length = 0n8, 
			unsigned int64 * args_object = 0x00000027`cbdfdb98, 
			class v8::internal::Isolate * isolate = 0x0000423d`00000000)+0x47 [c:\b\s\w\ir\cache\builder\src\v8\src\builtins\builtins-api.cc @ 131]

...and the resolved options for the event listener are:


0:000> dx -r1 ((chrome!blink::AddEventListenerOptionsResolved *)0x3ba382d30558)
((chrome!blink::AddEventListenerOptionsResolved *)0x3ba382d30558)                 : 0x3ba382d30558 [Type: blink::AddEventListenerOptionsResolved *]
    [+0x008] has_capture_     : true [Type: bool]
    [+0x009] capture_         : false [Type: bool]
    [+0x010] has_once_        : true [Type: bool]
    [+0x011] has_passive_     : true [Type: bool]
    [+0x012] once_            : false [Type: bool]
    [+0x013] passive_         : false [Type: bool]
    [+0x018] signal_          [Type: blink::Member<blink::AbortSignal>]
    [+0x020] passive_forced_for_document_target_ : false [Type: bool]
    [+0x021] passive_specified_ : false [Type: bool]

rc...@google.com <rc...@google.com> #16Apr 15, 2021 01:55AM

Status: Assigned (reopened)

Thank you for waiting.

We have logged this issue internally to investigate further. Please note that we cannot give you any timelines, but you can star the issue to get notifications.

jh...@google.com <jh...@google.com> Jul 22, 2022 03:44PM

Status: Won't Fix (Not Reproducible)

co...@gmail.com <co...@gmail.com> #17Feb 16, 2023 09:12AM

Comment has been deleted.

Message last modified on Feb 16, 2023 09:13AM

to...@gmail.com <to...@gmail.com> #18Feb 25, 2023 03:09PM

really ? not reproducible ? . . . I did not had to search a lot to find this here

https://maps.googleapis.com/maps/api/js

c.ontouchstart = c.ontouchmove = c.ontouchend = c.ontouchcancel = function(d) {
  _.Gf(d);
  _.Hf(d)
} ;

This is a result from https://pagespeed.web.dev/ which is linked to google search console. (Image attached)

Message last modified on Feb 25, 2023 03:10PM

Sat Feb 25 2023 10:08:39 GMT-0500 (Ecuador Time).png

23 KB

View

Download

lu...@scantek.com.au <lu...@scantek.com.au> #19Feb 28, 2023 04:49PM

This definitely is still happening, can be checked in the documentation for embedded maps as well (scroll down to the section where a map is shown on-screen, upon loading and with devtools open the violation warnings will appear):

https://developers.google.com/maps/documentation/embed/embedding-map

The line that seems to trigger this is obfuscated, but seems marked as line 75 in utils.js:

        return function(c) {
            var d = a
              , e = b
              , f = !1;
            "mouseenter" == d ? d = "mouseover" : "mouseleave" == d ? d = "mouseout" : "pointerenter" == d ? d = "pointerover" : "pointerleave" == d && (d = "pointerout");
            if (c.addEventListener) {
                if ("focus" == d || "blur" == d || "error" == d || "load" == d || "toggle" == d)
                    f = !0;
                c.addEventListener(d, e, f)
            } else
                c.attachEvent && ("focus" == d ? d = "focusin" : "blur" == d && (d = "focusout"),
                e = Soa(c, e),
                c.attachEvent("on" + d, e));
            return {
                eventType: d,
                ne: e,
                capture: f
            }
        }
    }```

With the specific highlighted line being: `c.addEventListener(d, e, f)`

Screenshot 2023-03-01 at 12.48.00 am.png

297 KB

View

Download

le...@gmail.com <le...@gmail.com> #20Sep 28, 2023 05:55PM

Still having this problem with my embedded Google Map.
Could simply adding:
c.addEventListener(d, e, f, {passive: true})
Fix this problem for everyone?

Message last modified on Sep 28, 2023 05:56PM

pa...@gmail.com <pa...@gmail.com> #21Oct 16, 2023 07:42AM

Hello,

We are also getting 21 violations for non-passive event listeners in init.embed.js (chrome dev tools - touchstart, touchmove and mousewheel) after embedding google maps.
(

https://maps.gstatic.com/maps-api-v3/embed/js/54/9/intl/en_gb/init_embed.js)

Is there still no solution for this?

Thanks in advance

19...@gmail.com <19...@gmail.com> #22Oct 30, 2023 04:25AM

dopo aver inserito una google maps embed riscontro sul browser i stessi avvisi segnalati nel post iniziale sulla console, queste sono le mie righe di codice:" <div>
<iframe title="ci trovi qui" width="400" height="400" load="lazy" frameborder="0" src="

https://www.google.com/maps/embed/v1/place?q=place_id:ChIJdeR-jZmJJRMRoOHHlSIMlxo&key=xxxxxxxxxxxxxxxxxxxxxxxx"
allowfullscreen></iframe>
</div>--> " al posto delle xxxxxxxxxxxxxxxxxxxxx c'è la mia key. mettendo  la console del browser non segnala più nessun avviso, ma ovviamente non si vede più la mappa.... come risolvo?

jo...@xmeasures.com <jo...@xmeasures.com> #23Nov 23, 2023 11:26PM

This is 100% happening and reproducable for me with Google Maps API v3 usage, outside of any frameworks whatsoever, in vanilla JS, when loaded via the preferred way:

<script>(g=>{var h,a,k,p="The Google Maps JavaScript API",c="google",l="importLibrary",q="__ib__",m=document,b=window;b=b[c]||(b[c]={});var d=b.maps||(b.maps={}),r=new Set,e=new URLSearchParams,u=()=>h||(h=new Promise(async(f,n)=>{await (a=m.createElement("script"));e.set("libraries",[...r]+"");for(k in g)e.set(k.replace(/[A-Z]/g,t=>"_"+t[0].toLowerCase()),g[k]);e.set("callback",c+".maps."+q);a.src=`https://maps.${c}apis.com/maps/api/js?`+e;d[q]=f;a.onerror=()=>h=n(Error(p+" could not load."));a.nonce=m.querySelector("script[nonce]")?.nonce||"";m.head.append(a)}));d[l]?console.warn(p+" only loads once. Ignoring:",g):d[l]=(f,...n)=>r.add(f)&&u().then(()=>d[l](f,...n))})({
key: "YOUR_API_KEY",
v: "weekly",
// Use the 'v' parameter to indicate the version to use (weekly, beta, alpha, etc.).
// Add other bootstrap parameters as needed, using camel case.
});
</script>

Then rendering directions via the DirectionsRenderer after importing the 'routes' library:

const { DirectionsService, DirectionsRenderer } = await google.maps.importLibrary('routes');
const directionsService = new DirectionsService();
const directionsDisplay = new DirectionsRenderer();
const directionsOptions = {
  map: mapDrawing, // the Google Map reference, set elsewhere via: new Map(el, options);
  panel: document.getElementById('directionsPanel'), // where should the driving directions display?
  markerOptions: marker // basic Marker, set elsewhere
};

const request = {
  origin: startGeolocation, // set elsewhere
  destination: endGeolocation, // set elsewhere
  travelMode: google.maps.DirectionsTravelMode.DRIVING,
  unitSystem: google.maps.UnitSystem.METRIC
};
directionsDisplay.setOptions(directionsOptions);
directionsService.route(request, function (resp, status) {
   if (status === 'OK') {
     directionsDisplay.setDirections(resp);
   } else {
     console.warn('DID NOT work! notok');
   }
});

I would love to code up a JS fiddle, but need an API Key to do so (and I'm not exposing mine!). I am baffled by the lack of acknowledgment of the issue, and insulted by the status "Won't fix (Not reproducible)" when CLEARLY it is being reproduced by so many people in 2023 alone.

Message last modified on Nov 24, 2023 05:04PM

co...@spencerplanton.com <co...@spencerplanton.com> #24Dec 16, 2023 12:54PM

I am reproducing the issue as well.
The google API needs to use passive listeners as per "c.addEventListener(d, e, f, {passive: true})" above.

Utterly crazy not to address passive listener issues which are causing warnings all over user applications.

Message last modified on Dec 16, 2023 12:54PM

jh...@google.com <jh...@google.com> May 28, 2024 08:25PM

Status: New

ka...@google.com <ka...@google.com> May 28, 2024 11:44PM

Assigned to ka...@google.com.

ra...@gmail.com <ra...@gmail.com> #25Jun 6, 2024 08:10AM

I'm experiencing this as well. Just opened a ticket, that I see now is a duplicate of this. https://issuetracker.google.com/issues/345359069

sa...@lau.do <sa...@lau.do> #26Jun 21, 2024 05:14AM

Also experiencing this.

ka...@google.com <ka...@google.com> #27Oct 31, 2024 07:17AM

Marked as fixed.

We greatly appreciate your patience.

We believe that all the passive event warning in Maps JS should be now fixed. Please let us know if the issue is still recurring on your end.

For Maps Embed API, the fix will be included 3.59 release. That being said, we will now be closing this issue.

Thanks for working with us!

IssueTracker

Maps API not using passive event listeners, generating console warnings

Status Update

Description

Describe your issue

> google.maps.version

What steps will reproduce the problem? Please also provide a code sample which demonstrates your issue (e.g. via jsfiddle.net, or jsbin.com)

Comments

rc...@google.com <rc...@google.com> #2Mar 31, 2021 07:19AM

te...@gmail.com <te...@gmail.com> #3Apr 1, 2021 05:55AM

te...@gmail.com <te...@gmail.com> #4Apr 3, 2021 12:39AM

rc...@google.com <rc...@google.com> #5Apr 3, 2021 12:43AM

rc...@google.com <rc...@google.com> #6Apr 3, 2021 12:46AM

rc...@google.com <rc...@google.com> #7Apr 6, 2021 04:08AM

te...@gmail.com <te...@gmail.com> #8Apr 6, 2021 03:39PM

te...@gmail.com <te...@gmail.com> #9Apr 6, 2021 03:42PM

rc...@google.com <rc...@google.com> #10Apr 7, 2021 03:13AM

te...@gmail.com <te...@gmail.com> #11Apr 7, 2021 09:00PM

te...@gmail.com <te...@gmail.com> #12Apr 7, 2021 09:09PM

rc...@google.com <rc...@google.com> #13Apr 8, 2021 03:04AM

te...@gmail.com <te...@gmail.com> #14Apr 12, 2021 07:56PM

te...@gmail.com <te...@gmail.com> #15Apr 12, 2021 09:23PM

rc...@google.com <rc...@google.com> #16Apr 15, 2021 01:55AM

jh...@google.com <jh...@google.com> Jul 22, 2022 03:44PM

co...@gmail.com <co...@gmail.com> #17Feb 16, 2023 09:12AM

to...@gmail.com <to...@gmail.com> #18Feb 25, 2023 03:09PM

lu...@scantek.com.au <lu...@scantek.com.au> #19Feb 28, 2023 04:49PM

le...@gmail.com <le...@gmail.com> #20Sep 28, 2023 05:55PM

pa...@gmail.com <pa...@gmail.com> #21Oct 16, 2023 07:42AM

19...@gmail.com <19...@gmail.com> #22Oct 30, 2023 04:25AM

jo...@xmeasures.com <jo...@xmeasures.com> #23Nov 23, 2023 11:26PM

co...@spencerplanton.com <co...@spencerplanton.com> #24Dec 16, 2023 12:54PM

jh...@google.com <jh...@google.com> May 28, 2024 08:25PM

ka...@google.com <ka...@google.com> May 28, 2024 11:44PM

ra...@gmail.com <ra...@gmail.com> #25Jun 6, 2024 08:10AM

sa...@lau.do <sa...@lau.do> #26Jun 21, 2024 05:14AM

ka...@google.com <ka...@google.com> #27Oct 31, 2024 07:17AM

Issue 184059401

Description

Describe your issue

> google.maps.version

What steps will reproduce the problem? Please also provide a code sample which demonstrates your issue (e.g. via jsfiddle.net, or jsbin.com)

Issue summary

Comments

rc...@google.com <rc...@google.com> #2Mar 31, 2021 07:19AM

te...@gmail.com <te...@gmail.com> #3Apr 1, 2021 05:55AM

te...@gmail.com <te...@gmail.com> #4Apr 3, 2021 12:39AM

rc...@google.com <rc...@google.com> #5Apr 3, 2021 12:43AM

rc...@google.com <rc...@google.com> #6Apr 3, 2021 12:46AM

rc...@google.com <rc...@google.com> #7Apr 6, 2021 04:08AM

te...@gmail.com <te...@gmail.com> #8Apr 6, 2021 03:39PM

te...@gmail.com <te...@gmail.com> #9Apr 6, 2021 03:42PM

rc...@google.com <rc...@google.com> #10Apr 7, 2021 03:13AM

te...@gmail.com <te...@gmail.com> #11Apr 7, 2021 09:00PM

te...@gmail.com <te...@gmail.com> #12Apr 7, 2021 09:09PM

rc...@google.com <rc...@google.com> #13Apr 8, 2021 03:04AM

te...@gmail.com <te...@gmail.com> #14Apr 12, 2021 07:56PM

te...@gmail.com <te...@gmail.com> #15Apr 12, 2021 09:23PM

rc...@google.com <rc...@google.com> #16Apr 15, 2021 01:55AM

jh...@google.com <jh...@google.com> Jul 22, 2022 03:44PM

co...@gmail.com <co...@gmail.com> #17Feb 16, 2023 09:12AM

to...@gmail.com <to...@gmail.com> #18Feb 25, 2023 03:09PM

lu...@scantek.com.au <lu...@scantek.com.au> #19Feb 28, 2023 04:49PM

le...@gmail.com <le...@gmail.com> #20Sep 28, 2023 05:55PM

pa...@gmail.com <pa...@gmail.com> #21Oct 16, 2023 07:42AM

19...@gmail.com <19...@gmail.com> #22Oct 30, 2023 04:25AM

jo...@xmeasures.com <jo...@xmeasures.com> #23Nov 23, 2023 11:26PM

co...@spencerplanton.com <co...@spencerplanton.com> #24Dec 16, 2023 12:54PM

jh...@google.com <jh...@google.com> May 28, 2024 08:25PM

ka...@google.com <ka...@google.com> May 28, 2024 11:44PM

ra...@gmail.com <ra...@gmail.com> #25Jun 6, 2024 08:10AM

sa...@lau.do <sa...@lau.do> #26Jun 21, 2024 05:14AM

ka...@google.com <ka...@google.com> #27Oct 31, 2024 07:17AM

Add comment

Issue metadata