On 9/2/13, Andrea Pescetti <pesce...@apache.org> wrote: > In the last few weeks we've seen users unable to see the big "Download" > button in http://www.openoffice.org/download/ due to broken (but still > used) browsers that failed to parse the JavaScript correctly. And > http://www.openoffice.org/download/other.html cannot be used as a > fallback due to the same issue. > > The JavaScript in other.html is used only to generate the page content, > and the result is independent of the user's browser: as Marcus > explained, it is there for convenience in creating the page.
How are we using the <noscript> tag within others? and which kind of content is it trying to plug? > Would it make sense to do the following? > > 1) Add an "All Apache OpenOffice downloads" link in the right-hand-side > column of http://www.openoffice.org/download/ near the top: this way, we > ensure that browsers with poor JavaScript support still display the link. Problaby the quicker solution, still is just a patch instead of just doing good webdev. > 2) Rename other.html to other_js.html This is a bad idea, I've seen many alternative clones being unmantained by webmasters. > 3) Modify other.html by pasting the actual download table (can be > retrieved, for example, with Firebug from other_js.html) in its HTML. > > This way we add a manual step (step 3) once per release, but we can be > sure that virtually all users can download OpenOffice in all cases > (working JavaScript, no JavaScript, broken JavaScript). > > Regards, > Andrea. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
