funny chromium "issue"

[virtualgadjo]

Hi all,

i've just ran into a funny issue, playing with pagination, htmx and that kind of thing in many different situations, i've a page containing a repeater called "zirepeater"
it will be easier to explain with those few lines

// $zirep = $pages->find("template=repeater_zirepeater, start=$start, limit=$limit");
// $zirep = $pages->find('template=repeater_zirepeater');
// $zirep = $pages->find('parent=1066');
$zirep = $page->zirepeater->find("start=$start, limit=$limit");

// and below in the template
print_r($zirep);

with the first three lines, firefox print_r a nice result in which i can read
[template] => repeater_zirepeater
so i assume my query is not that dumb 🙂 but in chrome, brave or edge i get
---
ProcessWire\PageArray Object ( [count] => 0 [items] => Array ( ) [selectors] => template=repeater_zirepeater )
ProcessWire\PageArray Object ( [count] => 0 [total] => 0 [start] => 0 [limit] => 2 [pager] => 0 à 0 de 0 [items] => Array ( ) [selectors] => template=repeater_zirepeater, start=0, limit=2 )
ProcessWire\PageArray Object ( [count] => 0 [items] => Array ( ) [selectors] => parent=1066 )
---
depending on the query, funny isn't it, firefox is more pw friendly and understands pw way of dealing with repeater page when chromium don't even if they get the selectors well

more a surprise than an issue as the uncommented line works with all of them but just in case it could be useful for someone playing with the same kind of things

and yes i like playing with pagination and/or htmx load more with nearly everything, galleries, repeaters, children pages, external db table query results (very useful with hundreds of lines...), well, all what pw lets me play with, that's to say everything 🙂

have a nice day