[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:  accepted
 Priority:  highest omg bbq  |   Milestone:  3.8
Component:  Appearance       |     Version:  trunk
 Severity:  blocker          |  Resolution:
 Keywords:                   |
-----------------------------+-----------------------

Comment (by adamsilverstein):

 Replying to [comment:7 matt]:
 > If there is a specific use case we want to support, like activating a
 theme that breaks JS and you can no longer deactivate it, perhaps we could
 constrain the no-js functionality to something small like that: Text
 listing of current theme and a deactivate link.
 >
 > This ticket isn't the time or place to debate it, but it's interesting
 to think about where we draw the line functionally as wp-admin shifts to
 be basically a JS application passing data back and forth to PHP rather
 than HTML whether it's worth it to essentially write everything twice, or
 leave the existing legacy HTML interfaces as gradually every screen in wp-
 admin, and the majority of the admin codebase, becomes client-side
 javascript.

 Yea! I am all for switching the admin to primarily JS tied to a PHP
 backend and glad to hear you are thinking along the same lines! I can
 envision the day when the page never 'reloads' from the moment you hit the
 login screen. I agree we would be better off with nojs support of only the
 most basic, required features.

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