diff --git a/src/_includes/layouts/base.njk b/src/_includes/layouts/base.njk index 632691ab..f6e15579 100644 --- a/src/_includes/layouts/base.njk +++ b/src/_includes/layouts/base.njk @@ -171,7 +171,7 @@ diff --git a/src/documents/ContextAwareness.md b/src/documents/ContextAwareness.md index ee894cc7..ed1ccbbf 100644 --- a/src/documents/ContextAwareness.md +++ b/src/documents/ContextAwareness.md @@ -44,7 +44,7 @@ of: ## Simple example - speech API-aware component This simple example invokes the `fluid.textToSpeech.isSupported` feature detector, which returns `true` if the current -browser supports the [HTML5 Speech API](https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html). We use the +browser supports the [HTML5 Speech API](https://wicg.github.io/speech-api/). We use the `fluid.contextAware.makeChecks` function to assign the result of this feature detection to a _context_ named `fluid.supportsTTS`. We can then use this context to conditionally switch in an extra [grade name](ComponentGrades.md), `examples.myComponent.speechAware` into the `examples.myComponent` component: diff --git a/src/documents/Contexts.md b/src/documents/Contexts.md index d42bd5d3..8bd0131f 100644 --- a/src/documents/Contexts.md +++ b/src/documents/Contexts.md @@ -27,7 +27,7 @@ Context names are derived both from particular components in the tree which have (ancestors) and the __*static environment*__. The static environment can be thought of as a set of contexts which are global to the entire application (that is, a context managed by the JavaScript virtual machine operated by the runtime - for example that derived from a browser frame or -[V8 context](https://developers.google.com/v8/embed#contexts)). These names can be matched by the +[V8 context](https://v8.dev/#contexts)). These names can be matched by the names appearing in curly brackets at the beginning of EL path expressions like `"{contextName}.furtherPath"`. Each component in the tree can give rise to a context name through three strategies: diff --git a/src/documents/IoCTestingFramework.md b/src/documents/IoCTestingFramework.md index 02561e86..ac65a661 100644 --- a/src/documents/IoCTestingFramework.md +++ b/src/documents/IoCTestingFramework.md @@ -66,8 +66,8 @@ configuration defining the sequence and structure of a group of test cases which ### `modules`, `tests` and `sequence` The standard structure inside a `fluid.test.testCaseHolder` has an outer layer of containment, `modules`, with members -corresponding to QUnit [modules](https://api.qunitjs.com/QUnit.module/), and within that an entry named `tests`, holding -an array of structures corresponding to QUnit [test](https://api.qunitjs.com/QUnit.test/). In ordinary use, each element +corresponding to QUnit [modules](https://qunitjs.com/api/QUnit/module/), and within that an entry named `tests`, holding +an array of structures corresponding to QUnit [test](https://qunitjs.com/api/QUnit/test/). In ordinary use, each element `tests` then contains a member named `sequence` holding a list of [*fixture records*](#supported-fixture-records). As well as containing a flat list of fixture records, `sequence` may also contain nested arrays of such records. These diff --git a/src/documents/PromisesAPI.md b/src/documents/PromisesAPI.md index 05e25faf..a6faa6e0 100644 --- a/src/documents/PromisesAPI.md +++ b/src/documents/PromisesAPI.md @@ -9,7 +9,7 @@ requiring I/O) or fallibly. JavaScript enjoys numerous competing libraries imple [Bluebird](https://github.com/petkaantonov/bluebird) as well as even multiple competing promise standards, such as [Promises/A+](https://promisesaplus.com/) and others from [CommonJS](https://wiki.commonjs.org/wiki/Promises). Promises are even built into an upcoming version of the JavaScript language itself, -[ES6](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Promise). +[ES6](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise). Infusion required an extremely simple implementation which can evolve independently, as well as begin the process of merging with the general declarative facilities of [Infusion IoC](HowToUseInfusionIoC.md) and hence become invisible as diff --git a/src/documents/ResourceLoader.md b/src/documents/ResourceLoader.md index 63e865d9..8fd42f0f 100644 --- a/src/documents/ResourceLoader.md +++ b/src/documents/ResourceLoader.md @@ -109,7 +109,7 @@ it is an Object with keys described in the [section on resourceSpecs](#resources locale Specifies the language code with the desired localization. Language codes are expected in a form - similar to BCP 47 tags but with a "_" instead of a "-" separating + similar to BCP 47 tags but with a "_" instead of a "-" separating the language code from the country code. When specified, the resource loader will add a suffix of the locale value to each entry defined in the resources and look for them at the first attempt. If any such resource is not located, the resource loader follows diff --git a/src/documents/TextToSpeechAPI.md b/src/documents/TextToSpeechAPI.md index 32a6a57f..ea629a58 100644 --- a/src/documents/TextToSpeechAPI.md +++ b/src/documents/TextToSpeechAPI.md @@ -4,12 +4,12 @@ category: Components --- The **Text To Speech** component uses [Web Speech Synthesis -API](https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#tts-section) to queue up and read texts. +API](https://wicg.github.io/speech-api/#tts-section) to queue up and read texts. ## Browser Support The Text To Speech component can be used in browsers that support [Web Speech Synthesis -API](https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#tts-section). At the time of writing, July 26 +API](https://wicg.github.io/speech-api/#tts-section). At the time of writing, July 26 2016, these browsers include: * Chrome 31+ @@ -21,7 +21,7 @@ API](https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#tts-sectio
Note: find the latest browser support data for Web Speech Synthesis API from caniuse.com. + href="https://caniuse.com/speech-recognition">caniuse.com.
## Creator @@ -376,7 +376,7 @@ speech: Configuration of the Text To Speech component can be done through `model.utteranceOpts`. This model path is a Javascript object that contains attributes that users can use to define the behaviour of the [SpeechSynthesisUtterance -instance](https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#utterance-attributes) (a part of the web +instance](https://wicg.github.io/speech-api/#utterance-attributes) (a part of the web speech API that the Text To Speech component interacts with).
@@ -465,16 +465,16 @@ fluid.textToSpeech({ Description The voice attribute must be a SpeechSynthesisVoice + href="https://wicg.github.io/speech-api/#speechsynthesisvoice">SpeechSynthesisVoice object that specifies the speech synthesis voice that the web application wishes to use. Calling the getVoices method returns an array of all available voices, from which you can select a valid SpeechSynthesisVoice, or you can call the SpeechSynthesis.getVoices() + href="https://wicg.github.io/speech-api/#dom-speechsynthesis-getvoices">SpeechSynthesis.getVoices() function of the browser directly.
Note: in some browsers (such as Chrome), the voice list is populated after the page is loaded, and you may need to wait for the voiceschanged + href="https://wicg.github.io/speech-api/#dom-speechsynthesis-onvoiceschanged">voiceschanged event to get a full list.
diff --git a/src/documents/tutorial-developerIntroduction/DeveloperIntroductionToInfusionFramework-OpeningRemarks.md b/src/documents/tutorial-developerIntroduction/DeveloperIntroductionToInfusionFramework-OpeningRemarks.md index 5a46ab50..b1971fcb 100644 --- a/src/documents/tutorial-developerIntroduction/DeveloperIntroductionToInfusionFramework-OpeningRemarks.md +++ b/src/documents/tutorial-developerIntroduction/DeveloperIntroductionToInfusionFramework-OpeningRemarks.md @@ -13,7 +13,7 @@ time. The introduction assumes: * You are familiar with the basics of [JavaScript](https://developer.mozilla.org/en-US/docs/Learn/JavaScript). -* You know how to use a browser's [developer tools](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_are_browser_developer_tools) +* You know how to use a browser's [developer tools](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/Tools_and_setup/What_are_browser_developer_tools) to access a console. * Ideally, you should also have some experience with the [jQuery](https://jquery.com/) JavaScript library that Infusion is built atop. diff --git a/src/documents/tutorial-prefsFrameworkMinimalFootprint/MinimalFootprint.md b/src/documents/tutorial-prefsFrameworkMinimalFootprint/MinimalFootprint.md index 158259b9..389bf036 100644 --- a/src/documents/tutorial-prefsFrameworkMinimalFootprint/MinimalFootprint.md +++ b/src/documents/tutorial-prefsFrameworkMinimalFootprint/MinimalFootprint.md @@ -11,11 +11,11 @@ optimizations. Below are some resources which discuss general website optimization strategies: -* [https://developers.google.com/speed/](https://developers.google.com/speed/) -* [https://developers.google.com/speed/docs/insights/rules](https://developers.google.com/speed/docs/insights/rules) -* [https://developers.google.com/web/fundamentals/performance](https://developers.google.com/web/fundamentals/performance) -* [https://www.smashingmagazine.com/2014/09/improving-smashing-magazine-performance-case-study/](https://www.smashingmagazine.com/2014/09/improving-smashing-magazine-performance-case-study/) -* [https://hpbn.co](https://hpbn.co) +* [Analyze and optimize your website with PageSpeed tools](https://developers.google.com/speed/) +* [Get Started with the PageSpeed Insights API](https://developers.google.com/speed/docs/insights/v5/get-started) +* [Why does speed matter?](https://web.dev/learn/performance/why-speed-matters) +* [Improving Smashing Magazine’s Web Performance: A Case Study](https://www.smashingmagazine.com/2014/09/improving-smashing-magazine-performance-case-study/) +* [High Performance Browser Networking](https://hpbn.co) ## Optimization of the Preferences Framework