This document:Public document·View comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group Other specs in this tool Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-2265 LC-2266 LC-2271 LC-2272 LC-2273 LC-2274 LC-2275 LC-2276 LC-2277 LC-2278 LC-2279 LC-2280 LC-2281 LC-2282 LC-2283 LC-2284 LC-2285 LC-2286 LC-2287 LC-2288 LC-2290 LC-2291 LC-2292 LC-2293 LC-2294 LC-2295 LC-2296 LC-2297 LC-2298 LC-2299 LC-2300
Previous: LC-2298 Next: LC-2282
3.4.11 I don't like this recommendation. What does "reasonable" mean? What about "manageable"? What is a 10Mb DOM? How should people measure it? Why was this value chosen? (Recent high end browser handle much larger DOMs) It is unclear what the recommendation to "Clip content and separate content onto separate pages" means. Are you saying to make top level URL changes to download new pages (and parse new JS)? If you are I think that is a bad recommendation as the latency hit is quite bad. Typically a better solution is to rather than hide non visible DOM elements, to instead remove these elements from the DOM altogether and recreate them as needed.