Re: Removing JavaScript from other.html
Am 09/05/2013 12:52 AM, schrieb Andrea Pescetti: On 02/09/2013 Marcus (OOo) wrote: Right, at the moment only the following has to be done to change the content of the other.html: - change the version number - change the languages - and if needed its order - change the platforms - and if needed its order But this wouldn't change. I managed to express myself very badly. In practice, what I propose is this: [details deleted] Hm, maybe as I've understood something completely different. ;-) What you now propose is a nice way to combine both - save time and ensure stable links. I'll give it a try on the coming weekend. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Removing JavaScript from other.html
On 02/09/2013 Marcus (OOo) wrote: Right, at the moment only the following has to be done to change the content of the other.html: - change the version number - change the languages - and if needed its order - change the platforms - and if needed its order But this wouldn't change. I managed to express myself very badly. In practice, what I propose is this: This is other_js.html (a copy of your current other.html) http://people.apache.org/~pescetti/tmp/2013-09-otherhtml/other_js.html This is the new other.html http://people.apache.org/~pescetti/tmp/2013-09-otherhtml/other.html See the difference? No? Good. other.html is obtained by opening in Firebug other_js.html and copy/pasting the table from there (from the document's DOM, not the HTML source that would have the write_table() function there). A few seconds' work. other_js.html is an internal convenience page, never shown to users or linked: it is a generator. So the workflow is unchanged, with the addition of a step that takes a few seconds: load other_js.html in Firefox and with Firebug copy the table to other.html. (you can use dozens of tools and techniques, I just picked one; if you want to script it you can use phantomjs or whatever, but everything is overkill for this). Then other.html will work for everybody and we can avoid dealing with broken browsers so long as they render HTML tables properly. I didn't clean up the noscript and other parts of other.html that would then be removed, but would be a simple one-time edit. All concerns about Google visibility are addressed too: actually, the new other.html would be more visibile to search engines that in general have difficulties in parsing JavaScript. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Removing JavaScript from other.html
On Mon, Sep 2, 2013 at 9:22 PM, sebb seb...@gmail.com wrote: AFAICT, there is *already* a really good candidate for the download/other.html page: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds The tables in the middle are easy to follow and AFAIK contain all the required information. No Javascript needed for the table itself. Can't the script which was used to create that content be tweaked a bit to create downloads/other.html? +1. Especially if this can be done at site-build time rather than as a browser runtime script. Or, since this data changes very slowly, it could be done as a manual script invocation, each time the data file is changed. We do that, for example, to maintain the consults list, with XSLT: http://www.openoffice.org/bizdev/consultants.html This was even localized. -Rob On 2 September 2013 22:26, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 09/02/2013 10:33 PM, schrieb Alexandro Colorado: On Mon, Sep 2, 2013 at 1:09 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 09/02/2013 06:51 PM, schrieb Alexandro Colorado: It also looks a bit 'dumb' that we dont have a link to others from the download page within our no script tag: Of course it doesn't make sense to refer to a page with JS when JS is disabled in the broeser. That's why there is no link to the webpage. downloads, need to provide a download link, that is just common sense. There is another problem with othes.html but not offering ANY link, is no solution. Sure, that's the reason why we are discussing how to ensure this for more users than now. Marcus On Mon, Sep 2, 2013 at 11:49 AM, Alexandro Coloradoj...@oooes.org wrote: On 9/2/13, Andrea Pescettipesce...@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/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.htmlhttp://www.openoffice.org/download/other.htmlcannot 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 thenoscript 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/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 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Removing JavaScript from other.html
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. 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. 2) Rename other.html to other_js.html 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
Re: Removing JavaScript from other.html
I suggest to checkout some of the many popular fallback libraries for browser compatibility. - modernizr - html5.js - svgweb.js - jquery - bootstrap - http://spoon.net/Browsers/ - https://browserlab.adobe.com/en-us/index.html On Mon, Sep 2, 2013 at 11:08 AM, Andrea Pescetti pesce...@apache.orgwrote: In the last few weeks we've seen users unable to see the big Download button in http://www.openoffice.org/**download/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.htmlhttp://www.openoffice.org/download/other.htmlcannot 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. 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/http://www.openoffice.org/download/near the top: this way, we ensure that browsers with poor JavaScript support still display the link. 2) Rename other.html to other_js.html 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-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org
Re: Removing JavaScript from other.html
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
Re: Removing JavaScript from other.html
It also looks a bit 'dumb' that we dont have a link to others from the download page within our no script tag: http://pastebin.mozilla.org/?diff=2959355 We never send people to other if JS is not working, let alone the language table. On Mon, Sep 2, 2013 at 11:49 AM, Alexandro Colorado j...@oooes.org wrote: 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 -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org
Re: Removing JavaScript from other.html
On Mon, Sep 2, 2013 at 9:08 AM, 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/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.htmlhttp://www.openoffice.org/download/other.htmlcannot 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. 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/http://www.openoffice.org/download/near the top: this way, we ensure that browsers with poor JavaScript support still display the link. 2) Rename other.html to other_js.html 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. I'm not sure it makes sense to provide 2 versions of download/other.html but I understand the JS concern. It might make sense to provide a script, housed in svn, to generate this table -- we had some other cases where this kind of technique was used in the past. It's not as neat as the JS that's being used now, but something to think about. So we would not have a JS generated table at all. --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- - MzK Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities. Truth isn't. -- Following the Equator, Mark Twain
Re: Removing JavaScript from other.html
Am 09/02/2013 06:08 PM, schrieb Andrea Pescetti: 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. 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. I don't think so because it would be too unremarkable. Better would be a bigger link with a more prominent location. 2) Rename other.html to other_js.html No, please don't do this. Even when the other.html is just the second choice, it is already very famous from the view point of the Google index: Google search with openoffice other.html -- 1st place with 1,780,00 hits. Google search with other.html -- 2nd place with 1,700,00,00 hits. Better would be an additional other_nojs.html webpage. But then the advantages of the normal other.html but be lapse. ;-) 3) Modify other.html by pasting the actual download table (can be retrieved, for example, with Firebug from other_js.html) in its HTML. Sorry, I don't know what you mean with pasting the table. 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). The very most users claiming about an invisible table on other.html. But they see the green box on index.html. So, I'm sure it must be a special thing with the table and no general JavaScript problem. However, until today I got no data that shows any hint to this problem. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Removing JavaScript from other.html
Am 09/02/2013 06:51 PM, schrieb Alexandro Colorado: It also looks a bit 'dumb' that we dont have a link to others from the download page within our no script tag: Of course it doesn't make sense to refer to a page with JS when JS is disabled in the broeser. That's why there is no link to the webpage. Marcus On Mon, Sep 2, 2013 at 11:49 AM, Alexandro Coloradoj...@oooes.org wrote: On 9/2/13, Andrea Pescettipesce...@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 thenoscript 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
Re: Removing JavaScript from other.html
Am 09/02/2013 06:49 PM, schrieb Alexandro Colorado: On 9/2/13, Andrea Pescettipesce...@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 thenoscript tag within others? and which kind of content is it trying to plug? Don't ask, just have a look into the webpage. ;-) 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. Just to leave no doubt. If we create new webpages, then we have to maintain them. Marcus 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
Re: Removing JavaScript from other.html
Am 09/02/2013 08:08 PM, schrieb Marcus (OOo): Am 09/02/2013 06:08 PM, schrieb Andrea Pescetti: 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. Right, at the moment only the following has to be done to change the content of the other.html: - change the version number - change the languages - and if needed its order - change the platforms - and if needed its order That's all. Maybe 5 minutes when typing and committing slow. ;-) No digging into the HTML code, no copy paste and no errors. no detailed tests for broken links which would take 1-2 hours if you do it seriously. That was the main reason for creating the other.html via JS. It's sad to see that it is not working as fine as I thought. 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. I don't think so because it would be too unremarkable. Better would be a bigger link with a more prominent location. 2) Rename other.html to other_js.html No, please don't do this. Even when the other.html is just the second choice, it is already very famous from the view point of the Google index: Google search with openoffice other.html -- 1st place with 1,780,00 hits. Google search with other.html -- 2nd place with 1,700,00,00 hits. Better would be an additional other_nojs.html webpage. But then the advantages of the normal other.html but be lapse. ;-) 3) Modify other.html by pasting the actual download table (can be retrieved, for example, with Firebug from other_js.html) in its HTML. Sorry, I don't know what you mean with pasting the table. 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). The very most users claiming about an invisible table on other.html. But they see the green box on index.html. So, I'm sure it must be a special thing with the table and no general JavaScript problem. However, until today I got no data that shows any hint to this problem. 4) Use a other_nojs.html webpage (practically the old other.html). Put a link to it into the today's other.html at top. Disadvantage: - It would doube the work for the moment. Advantage: - Fastest solution. - It gives time to investigate the real problem. Or find a better solution. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Removing JavaScript from other.html
On Mon, Sep 2, 2013 at 1:09 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 09/02/2013 06:51 PM, schrieb Alexandro Colorado: It also looks a bit 'dumb' that we dont have a link to others from the download page within our no script tag: Of course it doesn't make sense to refer to a page with JS when JS is disabled in the broeser. That's why there is no link to the webpage. downloads, need to provide a download link, that is just common sense. There is another problem with othes.html but not offering ANY link, is no solution. Marcus On Mon, Sep 2, 2013 at 11:49 AM, Alexandro Coloradoj...@oooes.org wrote: On 9/2/13, Andrea Pescettipesce...@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/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.htmlhttp://www.openoffice.org/download/other.htmlcannot 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 thenoscript 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/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-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org
Re: Removing JavaScript from other.html
Am 09/02/2013 10:33 PM, schrieb Alexandro Colorado: On Mon, Sep 2, 2013 at 1:09 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 09/02/2013 06:51 PM, schrieb Alexandro Colorado: It also looks a bit 'dumb' that we dont have a link to others from the download page within our no script tag: Of course it doesn't make sense to refer to a page with JS when JS is disabled in the broeser. That's why there is no link to the webpage. downloads, need to provide a download link, that is just common sense. There is another problem with othes.html but not offering ANY link, is no solution. Sure, that's the reason why we are discussing how to ensure this for more users than now. Marcus On Mon, Sep 2, 2013 at 11:49 AM, Alexandro Coloradoj...@oooes.org wrote: On 9/2/13, Andrea Pescettipesce...@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/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.htmlhttp://www.openoffice.org/download/other.htmlcannot 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 thenoscript 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/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
Re: Removing JavaScript from other.html
AFAICT, there is *already* a really good candidate for the download/other.html page: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds The tables in the middle are easy to follow and AFAIK contain all the required information. No Javascript needed for the table itself. Can't the script which was used to create that content be tweaked a bit to create downloads/other.html? On 2 September 2013 22:26, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 09/02/2013 10:33 PM, schrieb Alexandro Colorado: On Mon, Sep 2, 2013 at 1:09 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 09/02/2013 06:51 PM, schrieb Alexandro Colorado: It also looks a bit 'dumb' that we dont have a link to others from the download page within our no script tag: Of course it doesn't make sense to refer to a page with JS when JS is disabled in the broeser. That's why there is no link to the webpage. downloads, need to provide a download link, that is just common sense. There is another problem with othes.html but not offering ANY link, is no solution. Sure, that's the reason why we are discussing how to ensure this for more users than now. Marcus On Mon, Sep 2, 2013 at 11:49 AM, Alexandro Coloradoj...@oooes.org wrote: On 9/2/13, Andrea Pescettipesce...@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/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.htmlhttp://www.openoffice.org/download/other.htmlcannot 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 thenoscript 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/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 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
