[WIP] add forwards compatibility / graceful degradation principle. #468
Conversation
| @@ -294,6 +294,7 @@ Parts of the web platform evolve independently. | |||
| Issues that are present with a certain web technology now may be fixed in a subsequent iteration. | |||
| Duplicating these issues makes fixing them more difficult. | |||
| By adhering to this principle we can make sure overall platform quality improves over time. | |||
|
|
|||
There was a problem hiding this comment.
Vertical whitespace is useful. Why would you remove the space around the h2?
(A more serious problem here is the lack of content between the h2 and the first h3. That's very bad form.
| @@ -490,6 +491,120 @@ See also: | |||
| * [[#do-not-expose-use-of-assistive-tech]] | |||
| * [[#secure-context]] | |||
|
|
|||
| <h3 id=degrade-gracefully>Degrade Gracefully</h3> | |||
| <!-- was "Degrade Gracefully" in the HTML Design Principles --> | |||
|
|
|||
index.bs
Outdated
| @@ -490,6 +491,120 @@ See also: | |||
| * [[#do-not-expose-use-of-assistive-tech]] | |||
| * [[#secure-context]] | |||
|
|
|||
| <h3 id=degrade-gracefully>Degrade Gracefully</h3> | |||
There was a problem hiding this comment.
| <h3 id=degrade-gracefully>Degrade Gracefully</h3> | |
| <h3 id=degrade-gracefully>Degrade gracefully</h3> |
There was a problem hiding this comment.
I'm not sure that this text, which is very verbose, gets at the heart of the principle.
The key design decisions have already been made, so at best this is really explaining those decisions.
For instance, it was decided that an unrecognized HTML element would behave in a certain way; or that unknown CSS rules could be ignored; or that you need to check that a JS thingo exists before using it.
There are also things that apply to the use of Web-things that include consideration for the capabilities of the client, but I think we're not entirely within the remit of the document (modulo what Lea is doing for developers - there might be something to some adding some guidance there). However, most of those things require that someone act to ensure wide compatibility. Like checking for capabilities before using them, or like using polyfills (which obviously require that the fundamentals are implemented). Or they could just look at User-Agent and ship three versions of their site as seems to be increasingly common. Either way, I'm not sure that this is the place to start a dissertation on the subject.
| @@ -294,6 +294,7 @@ Parts of the web platform evolve independently. | |||
| Issues that are present with a certain web technology now may be fixed in a subsequent iteration. | |||
| Duplicating these issues makes fixing them more difficult. | |||
| By adhering to this principle we can make sure overall platform quality improves over time. | |||
|
|
|||
There was a problem hiding this comment.
Vertical whitespace is useful. Why would you remove the space around the h2?
(A more serious problem here is the lack of content between the h2 and the first h3. That's very bad form.
Oh, indeed. This is just a cut-and-paste of the text from the old HTML design principle. I've not posted anything worth reviewing yet. |
plinss
added
the
Status: In Progress
Fixes #175.
Preview | Diff