On Jul 5, 2011, at 6:38 PM, Brian W wrote: > Remy, > > Where in the TracDev Wiki can I find these guidelines? What is the reason to > still support non-JavaScript users? I understand people may use plugins like > NoScript, but a user of Trac can be informed via a <noscript> tag if > JavaScript is required even though this isn't quite as graceful. My main > reason for asking is in regards to plugins. Even though you say a plugin can > do what they want, understanding the motivation for Trac's graceful > degradation guideline may help inspire a plugin developer to do the same. If > a Trac instance with several plugins installed violates a Trac core principle > by introducing a JavaScript requirement, then I feel like it would undermine > your efforts.
Supporting non-JS also generally encourages saner designs, especially around things like accessibility. Is there something in Trac that would be noticeably improved by requiring JS? --Noah -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
