mirror of
https://github.com/moparisthebest/xeps
synced 2025-03-03 10:02:00 -05:00
0062f6c185
While a draft "standard" of the CSS Working Group of the W3C (as much as any W3C "living document" is a "standard" in any meaning of the word) says in a (non normative) section that both semicolon and comma are allowed [1], the MDN has the following thing to say [2]: > To mitigate this problem of virtual viewport […], Apple introduced > the "viewport meta tag" […]. Apple's documentation does a good job > explaining how web developers can use this tag, but we had to do > some detective work to figure out exactly how to implement it in > Fennec. For example, Safari's documentation says the content is a > "comma-delimited list," but existing browsers and web pages use > any mix of commas, semicolons, and spaces as separators. This leaves us to believe that although some W3C document says that both are ok, comma is the more portable choice. [1]: https://drafts.csswg.org/css-device-adapt/#viewport-meta [2]: https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag
XMPP Extension Protocols (XEPs)
About
This repository is used to manage work on XMPP Extension Protocols (XEPs), which are the specifications produced by the XMPP Standards Foundation (XSF). See http://xmpp.org/ for details. The rendered documents can be found here:
Contribution
Please use this repository to raise issues and submit pull requests:
https://github.com/xsf/xeps/issues https://github.com/xsf/xeps/pulls
For in-depth technical discussion, please post to the standards@xmpp.org email list:
https://mail.jabber.org/mailman/listinfo/standards
To submit a new proposal for consideration as a XEP, please read this page:
https://xmpp.org/about/standards-process.html#submitting-a-xep
XEP-0001: XMPP Extension Protocols defines the standards process followed by the XMPP Standards Foundation.
Editor
Documentation for Editors is in the docs folder.