Re: [greasemonkey-users] Re: Selector stops working while running script.

[كوميدي Yemen‎]

لم افهم مالمشكله عندما اذهب لصفحه يرفض الدخول لها 

هووووكه

في أحد، ١٤ سبتمبر، ٢٠٢٥ في ١٠:٠٠ ص، كتب I use userscripts <theinsc...@gmail.com>:

And a week later it just started working again.  No explanation on either end of it.

On Wednesday, 9 April 2025 at 21:19:31 UTC I use userscripts wrote:

I have a script that used to work...

Selecting a detail record under

https://www.kroger.com/mypurchases

(also works on https://www.dillons.com/mypurchases )

There is a field that says something like "In-store March 26"

The selector for that field is

$( "h2.kds-Heading.kds-Heading--m.my-0" ).outerText

I can use this in the Watch Expressions or the console command line in the Firefox debugger.

But as soon as I run the script, with a break point set on

var tripDate = $( "h2.kds-Heading.kds-Heading--m.my-0" ).outerText

Not only does tripDate come up "undefined" the watch list also shows that selector as undefined.

The field is still present on screen.  I don't understand why the selector stops seeing that DOM element.

I'm fairly proficient with JavaScript, but this has me stumped.

I'm using jQuery v3.5.1 that is bundled with the script.

I am attempting to update the script, the previous selector, before they changed the site was

var tripDate = $( "span:contains('Order date:')" ).find( 'br' ).get(0).nextSibling.nextSibling.nodeValue

--
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to greasemonkey-us...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/greasemonkey-users/44e10d40-91a4-428b-bda2-99777d86aa69n%40googlegroups.com.

[كوميدي Yemen‎]

لماذا لم احصل على الخادم لم تفتح الصفحه في المتصفح 

هووووكه

في جمعة، ١٩ سبتمبر، ٢٠٢٥ في ١٢:١٩ ص، كتب I use userscripts <theinsc...@gmail.com>:

DOM has to be readable or there is no page for the browser to render.

The fact that JavaScript was unable to select an element of DOM was just weird.

It had worked before and it works now, but for a few days there it would not work.  Firefox did receive an update since then, so perhaps a bug in the JS engine?

To view this discussion visit https://groups.google.com/d/msgid/greasemonkey-users/e8206cbd-9201-4321-a227-d2f6046a69c1n%40googlegroups.com.