Member Avatar for omsoni

This issue only happens in FF (IE and Chrome seem to work fine).

I have a Spry paged dataset (at bottom of page with big blue arrows.)

dealpigeon dot com/indexMore.php

When I change the page in a paged region (by clicking on arrow), it is refreshed as expected.

But in FF another unrelated DIV above the region is also getting refreshed. Which is annoying to see. I do not want my users to have that experience.

This is stopping me from moving this page to production.
Please help, I am clueless as to why this is happening.

Thanks,

  • 2 Contributors
  • 3 Replies
  • 114 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Phaelax

Dani AI

Generated

This symptom (Firefox updating an unrelated DIV when the Spry paged dataset changes) usually points to a DOM mutation or reparse that affects more of the document than intended. was on the right track suggesting a markup/console check — invalid HTML, duplicate IDs or a region boundary that overlaps the DIV above are common cross‑browser traps. Start by confirming JavaScript is actually enabled in the browser and that the Firefox console shows no hard errors at the moment you click the paging control.

Practical, low-effort checks to run now:

  • Validate the page HTML with the W3C validator to catch unclosed tags or structural problems: W3C Validator.
  • In Firefox DevTools, right‑click the DIV that “refreshes” and choose Break on → Subtree modifications (or use a DOM breakpoint). Then trigger the pager and see which script/location pauses in the debugger.
  • Watch Network and Console panels for XHRs or runtime errors when paging.
  • Use a quick MutationObserver in the console to log which nodes change, for example:
var mo = new MutationObserver(function(muts){ muts.forEach(function(m){ console.log(m.type, m.target); }); });
mo.observe(document.body, {subtree:true, childList:true});

If the observer shows the unexpected DIV being rewritten, track the call stack in the paused debugger to the exact function doing the replacement.

Fixes that tend to resolve this class of bug: correct any malformed HTML, remove duplicate IDs, and ensure the Spry update targets only the list container (or move the static DIV outside the DOM subtree Spry touches). If the problem persists after isolating a minimal test case, consider upgrading or replacing the widget or filing a bug with the Spry project. Further reading on how node assignment can reparse markup: Element.innerHTML and the MutationObserver API: MutationObserver.

Recommended Answers

All 3 Replies

Member Avatar for Phaelax

Without seeing the code, I can only guess, but I think there might be an unclosed tag somewhere. I'm not sure which DIV is refreshing, but when I look at the page in FF apart from Chrome, I do not get the deal list on the left. The dropdown box only shows {@desc} and lists 1 item {@line} with {@finalprice}. It's possible the other browsers see the same bug, but either ignore or are able to assume a correction and move on.

I opened up the FF error console and see the following:

Warning: Expected declaration but found '/'. Skipped to next declaration.
Source File:
Line: 382

Warning: Error in parsing value for 'filter'. Declaration dropped.
Source File:
Line: 952

Though I doubt this is a CSS issue, it does raise a flag of some possible areas to check in the code.

Member Avatar for omsoni

Phaelax,

That should not happen. You should see the site properly if you have javascript enabled. Site needs javascript.

Now I am more worried if you can't even see it.
Do you have javascript enabled ?

Thanks

Member Avatar for Phaelax

Well now I feel like a complete idiot, I forgot I disabled JS in FF the other day while working on another project.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.