IE10 pagination query bounding not honoring limit parameter

Goal

To verify that server‑side pagination parameters (offset, limit) are correctly transmitted and interpreted when accessing a large dataset from Internet Explorer 10.

Constraints and Uncertainty

IE10 does not expose a dedicated API for query bounding; pagination is typically driven by HTTP GET parameters. The browser may alter or cache requests, and JavaScript engines can coerce numeric values into strings or truncate large numbers. It is unclear whether the client automatically appends the expected parameters when a pagination control is used, or if the server must explicitly parse them.

Specific Questions

1. When a client‑side pagination component triggers a request, does IE10 include both offset and limit query parameters as specified?
2. Are there known IE10 bugs that modify numeric query values (e.g., converting 1000 to 1e3 or truncating beyond a certain size) before they reach the server?
3. Does IE10’s caching mechanism interfere with successive pagination requests, potentially causing stale data to be served?