FAQ - Revision history

Annevk: Replaced content with "{{moved|the [https://whatwg.org/faq WHATWG FAQ], the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ], and the [https://whatwg.org/mailing-list WHATWG..."

2018-01-24T17:34:29Z

Replaced content with "{{moved|the [https://whatwg.org/faq WHATWG FAQ], the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ], and the [https://whatwg.org/mailing-list WHATWG..."

← Older revision		Revision as of 17:34, 24 January 2018
Line 1:		Line 1:
	{{moved\|the [https://whatwg.org/faq WHATWG FAQ] ~~and~~ the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ]}}		{{moved\|the [https://whatwg.org/faq WHATWG FAQ], the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ], and the [https://whatwg.org/mailing-list WHATWG Mailing List] page.}}

	~~== Mailing List ==~~

	~~=== +1 ===~~

	~~Please note that content-free agreement (such as +1s) have no effect on~~
	~~the WHATWG list and are therefore discouraged. Editors of specs discussed~~
	~~in the WHATWG only consider the quality of the arguments presented~~, and
	~~not~~ the ~~volume of agreement.~~

	~~You should therefore only post to the list if you have a substantive new point~~
	~~to make, for example if you have seen a flaw in an argument presented so far,~~
	~~or have a new idea to contribute, or have some information that has not yet~~
	~~been brought to the table.~~

	~~=== Should I top-post or reply inline? ===~~

	~~'''Please reply inline or make the reply self-contained, and trim extraneous quotes from previous emails in your replies.'''~~

	Basically, please remove anything after the last line you have written, so that people don't have to scroll down to find out what else you wrote, and make sure that your email makes sense on its own, as it will probably be read out of context years later.

	~~That is, you should reply like this:~~

	~~<pre>~~
	~~Ian wrote~~:
	~~> What do you want?~~

	~~I want cats!~~

	~~> When do you want it?~~

	~~Now!~~
	</~~pre>~~

	~~You should definitely not reply like this (because this requires people to read your email backwards):~~

	~~<pre class="error" >~~
	No

	~~Ian wrote:~~
	~~> Is this a good example of how to post emails?~~
	</~~pre>~~

	~~You should also not reply like this (because this leaves people to wonder if there is any text lower down that you have written):~~

	~~<pre class="error" >~~
	~~This is a bad way to write email.~~

	~~Ian wrote:~~
	~~> Is this a good way to write email?~~
	~~> Lorem ipsum foo bar baz.~~
	~~> Unrelated other bits that aren't replied to~~.
	~~> Yet more text~~
	</~~pre>~~

	~~You should also not reply like this (with no context at all), because the reader will not know what you are referring to:~~

	~~<pre class="error" >~~
	~~No, I think that's a bad idea. It wouldn't be good for the readers, for instance.~~
	~~</pre>~~

	~~Quote enough original text or provide an introduction yourself~~.

Philipj: drop ?

2017-08-23T10:21:07Z

drop ?

← Older revision		Revision as of 10:21, 23 August 2017
Line 1:		Line 1:
	{{moved\|the [https://whatwg.org/faq? WHATWG FAQ] and the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ]}}		{{moved\|the [https://whatwg.org/faq WHATWG FAQ] and the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ]}}

	== Mailing List ==		== Mailing List ==

Philipj at 13:29, 11 August 2017

2017-08-11T13:29:32Z

← Older revision		Revision as of 13:29, 11 August 2017
Line 1:		Line 1:
	{{moved\|the [https://whatwg.org/faq?~~nocache~~ WHATWG FAQ] and the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ]}}		{{moved\|the [https://whatwg.org/faq? WHATWG FAQ] and the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ]}}

	== Mailing List ==		== Mailing List ==

Philipj: throw in ?nocache in until this thing is out of the cache

2017-08-11T13:28:48Z

throw in ?nocache in until this thing is out of the cache

← Older revision		Revision as of 13:28, 11 August 2017
Line 1:		Line 1:
	{{moved\|the [https://whatwg.org/faq WHATWG FAQ] and the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ]}}		{{moved\|the [https://whatwg.org/faq?nocache WHATWG FAQ] and the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ]}}

	== Mailing List ==		== Mailing List ==

Philipj: Drop Outlook question, it's very unlikely to be read and useful again

2017-08-11T13:26:14Z

Drop Outlook question, it's very unlikely to be read and useful again

← Older revision		Revision as of 13:26, 11 August 2017
Line 14:		Line 14:
	or have a new idea to contribute, or have some information that has not yet		or have a new idea to contribute, or have some information that has not yet
	been brought to the table.		been brought to the table.

	~~=== Making Outlook quote email messages properly ===~~
	If you use Outlook or Outlook Express, you can use either [http://home.in.tum.de/~jain/software/outlook-quotefix/ Outlook-QuoteFix] or [http://home.in.tum.de/~jain/software/oe-quotefix/ OE-QuoteFix]. These plugins fix several of Outlook's problems with sending properly formatted emails.

	=== Should I top-post or reply inline? ===		=== Should I top-post or reply inline? ===

Philipj: move to https://whatwg.org/faq

2017-08-11T13:25:35Z

move to https://whatwg.org/faq

Show changes

Philipj: move to https://github.com/whatwg/html/blob/master/FAQ.md

2017-08-10T11:36:31Z

move to https://github.com/whatwg/html/blob/master/FAQ.md

Show changes

Zcorpan: /* Is there a Code of Conduct? */

2017-06-14T09:50:35Z

Is there a Code of Conduct?

← Older revision		Revision as of 09:50, 14 June 2017
Line 34:		Line 34:
	=== Is there a Code of Conduct? ===		=== Is there a Code of Conduct? ===

	Yes, see [[Code of Conduct]]. Please read it and respect it.		Yes, see [https://whatwg.org/code-of-conduct Code of Conduct]. Please read it and respect it.

	== The WHATWG Process ==		== The WHATWG Process ==

Domenic: /* How do you spell and pronounce WHATWG? */

2017-05-24T01:38:04Z

How do you spell and pronounce WHATWG?

← Older revision		Revision as of 01:38, 24 May 2017
Line 9:		Line 9:
	=== How do you spell and pronounce WHATWG? ===		=== How do you spell and pronounce WHATWG? ===

	It is spelled WHATWG, all uppercase. It has various pronunciations: what-wee-gee, what-wig, what-double-you-gee.		It is spelled WHATWG, all uppercase, no spaces. It has various pronunciations: what-wee-gee, what-wig, what-double-you-gee.

	=== What is the WHATWG working on? ===		=== What is the WHATWG working on? ===

Annevk at 09:20, 13 March 2017

2017-03-13T09:20:07Z

← Older revision		Revision as of 09:20, 13 March 2017
Line 60:		Line 60:
	=== How should tool developers, screen reader developers, browser vendors, search engine vendors, and other implementors interact with the WHATWG? ===		=== How should tool developers, screen reader developers, browser vendors, search engine vendors, and other implementors interact with the WHATWG? ===

	File an issue on the [https://whatwg.org~~/specs~~/ relevant standard] as indicated at the top of that standard. All feedback is supposed to be addressed in due course. You are also welcome to take a stab at addressing the problem yourself through a GitHub pull request.		File an issue on the [https://spec.whatwg.org/ relevant standard] as indicated at the top of that standard. All feedback is supposed to be addressed in due course. You are also welcome to take a stab at addressing the problem yourself through a GitHub pull request.

	'''If you want feedback to be dealt with faster than "eventually", e.g., because you are about to work on that feature and need the spec to be updated to take into account all previous feedback, let the editors know''' by either emailing them, or contacting them on [[IRC]]. Requests for priority feedback handling are handled confidentially if desired so other implementers won't know that you are working on that feature.		'''If you want feedback to be dealt with faster than "eventually", e.g., because you are about to work on that feature and need the spec to be updated to take into account all previous feedback, let the editors know''' by either emailing them, or contacting them on [[IRC]]. Requests for priority feedback handling are handled confidentially if desired so other implementers won't know that you are working on that feature.
Line 178:		Line 178:
	The HTML Standard is available in two forms: [https://html.spec.whatwg.org/ single-page] (''very large'') and '''[https://html.spec.whatwg.org/multipage/ multi-page]'''.		The HTML Standard is available in two forms: [https://html.spec.whatwg.org/ single-page] (''very large'') and '''[https://html.spec.whatwg.org/multipage/ multi-page]'''.

	The WHATWG [https://whatwg.org~~/specs~~/ also works on other standards], such as the DOM, URL, and XMLHttpRequest standards.		The WHATWG [https://spec.whatwg.org/ also works on other standards], such as the DOM, URL, and XMLHttpRequest standards.

	The W3C publishes some forked versions of these specifications. We have requested that they stop publishing these but they have refused. They copy most of our fixes into their forks, but their forks are usually weeks to months behind. They also make intentional changes, and sometimes even unintentional changes, to their versions. We highly recommend not paying any attention to the W3C forks of WHATWG standards.		The W3C publishes some forked versions of these specifications. We have requested that they stop publishing these but they have refused. They copy most of our fixes into their forks, but their forks are usually weeks to months behind. They also make intentional changes, and sometimes even unintentional changes, to their versions. We highly recommend not paying any attention to the W3C forks of WHATWG standards.