[wp-trac] [WordPress Trac] #25964: Appearance Themes: find a way to provide a no-js fallback

[WordPress Trac]

#25964: Appearance Themes: find a way to provide a no-js fallback
-----------------------------+---------------------
 Reporter:  matveb           |       Owner:  nacin
     Type:  defect (bug)     |      Status:  closed
 Priority:  highest omg bbq  |   Milestone:  3.8
Component:  Appearance       |     Version:  trunk
 Severity:  blocker          |  Resolution:  fixed
 Keywords:                   |
-----------------------------+---------------------

Comment (by nacin):

 Syncing this single 33-line template is going to be really easy. But, I
 see a point in the future where the same PHP file can be used as a PHP
 template and, with minor transformations done automatically, a Backbone
 template. At you can see, the syntax is nearly the same. If bracket
 notation was used instead of object notation in this Backbone template,
 it'd be even closer. Some kind of template sharing is a bit of a wheel
 reinvention, but it avoids us unnecessarily diving into new templating
 languages for the moment. For now, [26726] works as a graceful fallback.
 Maybe a shared template could work for more things along these lines. Just
 something to think about.

 We've used a few different techniques when an entire legacy interface
 becomes JavaScript. We've left existing HTML interfaces (media), declared
 the whole thing a value-add you only get with JavaScript (revisions), and
 provided baseline behavior in no-JS mode (themes). This baseline behavior
 is also how the rest of WordPress already handles no-JS, and it was the
 clear best choice here, with the least amount of code and pain.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/25964#comment:11>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software