Index - Archive of obsolete content
283 introduction welcome to the xul school tutorial!
... 601 plug-n-hack get involved security, plugnhack while this project has been started by the mozilla security team and has been validated with firefox and owasp zap, this is an open project and we welcome involvement from anyone, especially people working on other browsers and security tools.
...comments or questions are welcome and encouraged via the tamarin-devel mailing list.
... 1813 xul accessibility guidelines accessibility, xul welcome to the xul accessibility guidelines.

Preferences - Archive of obsolete content
let's say you want to make the default value for the extensions.myext.welcomemessage preference localizable.
... you should do the following: add this line to some .properties file (for all of your locales), say to chrome://myext/locale/defaults.properties: extensions.myext.welcomemessage=localized default value add the default value for extensions.myext.welcomemessage, pointing to that properties file, by adding the following line to your file with default preferences (see below).
... pref("extensions.myext.welcomemessage", "chrome://myext/locale/defaults.properties"); read the preference with getcomplexvalue, passing nsipreflocalizedstring as atype: var prefs = components.classes["@mozilla.org/preferences-service;1"] .getservice(components.interfaces.nsiprefservice); var branch = prefs.getbranch("extensions.myext."); var value = branch.getcomplexvalue("welcomemessage", components.interfaces.nsipreflocalizedstring).data; the code in step 3 will read the default value from chrome://myext/locale/defaults.properties when no user value is set, and will behave exactly the same as if nsisupportsstring was passed as atype otherwise.

Creating a Help Content Pack - Archive of obsolete content
this attribute is optional, with fallback to the value welcome.
...the sample page chrome://help/locale/welcome.xhtml has a section on searching which may be a useful link to use here.
...recall that in the content pack descriptor file you included an nc:defaulttopic attribute, which defaulted to "welcome".

JavaScript basics - Learn web development
adding a personalized welcome message next, let's change the page title to a personalized welcome message when the user first visits the site.
... this welcome message will persist.
...we will also include an option to change the user, and therefore, the welcome message.

Ember app structure and componentization - Learn web development
this already exists, and its contents currently look like so: {{!-- the following component displays ember's default welcome message.
... --}} <welcomepage /> {{!-- feel free to remove this!
... --}} {{outlet}} <welcomepage /> is a component provided by an ember addon that renders the default welcome page we saw in the previous article, when we first navigated to our server at localhost:4200.

TypeScript support in Svelte - Learn web development
this is how the contents will end up: // stores.ts import { writable } from 'svelte/store' import { localstore } from './localstore.js' import type { todotype } from './types/todo.type' export const alert = writable('welcome to the to-do list app!') const initialtodos: todotype[] = [ { id: 1, name: 'visit mdn web docs', completed: true }, { id: 2, name: 'complete the svelte tutorial', completed: false }, ] export const todos = localstore('mdn-svelte-todo', initialtodos) remember to update the import statements in app.svelte, alert.svelte, and todos.svelte.
... if you open the file todos.svelte and assign a number type to our $alert store, you'll get the following error: that's because when we defined our alert store in the stores.ts file with: export const alert = writable('welcome to the to-do list app!') typescript inferred the generic type to be string.
... if we wanted to be explicit about it, we could do the following: export const alert = writable<string>('welcome to the to-do list app!') now we'll make our localstore store support generics.

Working with Svelte stores - Learn web development
give it the following content: import { writable } from 'svelte/store' export const alert = writable('welcome to the to-do list app!') note: stores can be defined and used outside of svelte components, so you can organize them in any way you please.
... in the above code we import the writable() function from svelte/store and use it to create a new store called alert with an initial value of "welcome to the to-do list app!".
... update stores.js like so: import { writable } from 'svelte/store' import { localstore } from './localstore.js' export const alert = writable('welcome to the to-do list app!') const initialtodos = [ { id: 1, name: 'visit mdn web docs', completed: true }, { id: 2, name: 'complete the svelte tutorial', completed: false }, ] export const todos = localstore('mdn-svelte-todo', initialtodos) using localstore('mdn-svelte-todo', initialtodos), we are configuring the store to save the data in web storage under the key mdn-svelte-todo.

Handling common accessibility problems - Learn web development
if you've not used vo before, you will be given a welcome screen where you can choose to start vo or not, and run through a rather useful tutorial to learn how to use it.
...you'll see the nvda welcome dialog when you start it.
...in the case of nvda, the modifier can either be insert (the default), or capslock (can be chosen by checking the first checkbox in the nvda welcome dialog before pressing ok).

HTMLElement.hidden - Web APIs
javascript document.getelementbyid("okbutton") .addeventlistener("click", function() { document.getelementbyid("welcome").hidden = true; document.getelementbyid("awesome").hidden = false; }, false); this code sets up a handler for the welcome panel's "ok" button that hides the welcome panel and makes the follow-up panel—with the curious name "awesome"—visible in its place.
... the welcome panel <div id="welcome" class="panel"> <h1>welcome to foobar.com!</h1> <p>by clicking "ok" you agree to be awesome every day!</p> <button class="button" id="okbutton">ok</button> </div> this html creates a panel (in a <div> block) that welcomes the user to a site and tells them what they're agreeing to by clicking the ok button.
... the follow-up panel once the user clicks the "ok" button in the welcome panel, the javascript code swaps the two panels by changing their respective values for hidden.

Troubleshooting - Archive of obsolete content
you're welcome to post a question, too.
... and if you'd like to report a bug in the sdk, that's always welcome!

Introduction - Archive of obsolete content
next » welcome to the xul school tutorial!
... welcome to the world of extension development.

The Essentials of an Extension - Archive of obsolete content
<em:name>xul school hello world</em:name> <em:description>welcome to xul school!</em:description> <em:version>0.1</em:version> <em:creator>appcoast</em:creator> <em:homepageurl>https://developer.mozilla.org/docs/xul_school</em:homepageurl> this is the data that is displayed before and after the extension is installed, that you can see in the add-ons manager.
... exercise make the following changes to the example extension: edit the welcome message that is displayed in the alert window.

JXON - Archive of obsolete content
es example #1: how to use jxon to create an html document instead of an xml document: /* the structure of my document */ var omyhtmlstruct = { "html": { "head": { "meta": { "@http-equiv": "content-type", "@content": "text/html; charset=utf-8" }, "title": "my html document", "script": { "@type": "text/javascript", "keyvalue": "alert(\"welcome!\");" }, "style": "p:first-letter {\n font: italic bold 30px georgia, serif;\n}" }, "body": { "h1": "my html document", "p": "hello world!!" } } }; /* create the document */ var omyhtmldoc = jxon.unbuild(omyhtmlstruct, "http://www.w3.org/1999/xhtml"); …and here is the output of alert((new xmlserializer()).serializetostring(omyhtmldoc)): <html> <head> ...
... <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <title>my html document</title> <script type="text/javascript"> alert("welcome!"); </script> <style> p:first-letter { font: italic bold 30px georgia, serif; } </style> </head> <body> <h1>my html document</h1> <p>hello world!!</p> </body> </html> note: as we already said in the note within code considerations, despite the bidirectional conversion between xml and json is lossless regarding the whole content and the structure of an xml document, it is not lossless regarding the ordering of elements, which for some xml dialects (like xhtml) is part of the information.

Mozilla Crypto FAQ - Archive of obsolete content
support for pgp and other security-related protocols and formats can potentially be added to mozilla in the same manner as ssl and s/mime; if anyone is interested in working on such support within the mozilla project then they are welcome to do so.
...if anyone is interested on working such support within the mozilla project then they are welcome to do so.

Mozilla release FAQ - Archive of obsolete content
people who want to work on an operating system no doubt would be welcomed by the bsd teams, the linux team, the freedows team, or any of the many other open source operating system groups out there.
...maintenance of old documentation would be helpful, new documentation is also welcome.