Changes

Jump to: navigation, search

Tantek

2,575 bytes removed, 02:42, 28 May 2016
move HTML5 support and documentation to HTML5 page, CSS Variables now a draft and implemented see https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_variables, misc minor edits
= Tantek Çelik =
<div class="h-card vcard">
'''<dfn class="p-name fn">Tantek Çelik</dfn>''' is a Mozilla employee (2011-176 to present) developing and coordinating work on web [[standards]]. Tantek is usually in the [[SF]] office MWF and occasionally in the [[Mountain View]] office. URLs and contact Contact info:
* <span class="u-url url">http://tantek.com/</span> - personal [[IndieWeb]] site
* [http://twitter.com/t @t] - Twitter
</div>
</div>
See also Tantek's User: page, where he puts various pieces of information that doesn't really merit showing up in default wiki search results (which exclude results from User: pages by default)
* [[User:Tantek]]
== projects ==
== contribute ==
* Want to work for Mozilla? http://mozilla.org/jobs
** Hint, by contributing you can meet people and find out more about working with Mozilla
* Contribute to Mozilla: http://mozilla.org/contribute
** By contributing you can meet people and find out more about working with Mozilla
Here's three things you can do to get started:
# get on IRC with Colloquy - see https://wiki.mozilla.org/Irc#Colloquy for details
# create an account on https://wiki.mozilla.org / and edit your user page
#* e.g. this is Tantek's: https://wiki.mozilla.org/User:Tantek
# create an account on http://bugzilla.mozilla.org/
== pages ==
Some breadcrumbs A few of the pages Tantek is adding to as a side-effect of his projects. These are obviously collaborative works - you are strongly encouraged to contribute to any that interest you.I've created in the past
* [[CSS3]]
** [[CSS3/color|color module]]
** [[HTML5/time|&lt;time&gt;]]
** ...
* [[Events]]
* [[SF]]
* [[Standards]]
** [[Standards/license]]
* ...
== ideas to explore ==
Some ideas to consider exploring. Tantek has not taken on these (yet). This is a place to collect potential tasks. Feel free to grab any of these and ask Tantek questions about suggested approach(es) etc.
 
=== HTML5 support and documentation ===
 
A few ideas for improving the understanding and adoption of Firefox's HTML5 support. Help is definitely encouraged on any / all of these. Want to help out? Feel free to edit this section, add suggestions with your name (please sign with <nowiki>~~~~</nowiki> ), and volunteer to help out.
 
The better we document and explain Firefox's HTML5 support, the more developers learn about it and put it to use in real world web apps, the more feedback we get on Firefox's HTML5 implementation and know what to improve and iterate on, etc. A key goal here is to encourage an ever stronger feedback loop that improves the state of the art of HTML5 Web App development in general, and in particular with building increasingly higher fidelity HTML5+CSS3 Web Apps with Firefox as a development platform.
 
Some specific tasks that would help:
 
* Increased documentation of Firefox's HTML5 support/efforts in general (per release). Each release (even dotrevs) should come with a link to a support chart (for HTML5, CSS3 at a minimum).
** expanding/updating https://developer.mozilla.org/en/HTML/HTML5
*** including https://developer.mozilla.org/en/HTML/HTML5/FAQ
* Public test cases that illustrate Firefox's HTML5 support
* Public support charts/tables summarizing Firefox's HTML5 support (linking to aforementioned test cases)
* A proper draft test suite constructed from those test cases (submit to W3C HTML WG)
* Implementation reports based on those test suites
* Perhaps a place to gather testimonials about Firefox's HTML5 support
 
See also: Top level [[HTML5]] page on this wiki.
=== additional potential CSS work ===
* '''CSS variables.''' Use case for CSS variables from Joe Walker: <blockquote><p>With Bespin, we're using less.js because CSS by itself can't handle themes and plugins. Having independent parts of the program describe the theme and the thing that should be themed requires something external to both. The obvious solution is CSS variables.</p><p>Put it another way - one part of Bespin provides customizable themes. That part knows nothing about the command line part, which wants to know how to paint itself. If we can have the command line use a CSS variable called @bespin-background, then this can be fulfilled by the theme.</p></blockquote>
 
* '''Proposing -moz- innovations.''' There are numerous -moz- innovations like selectors (e.g. [https://developer.mozilla.org/en/CSS/:-moz-broken :-moz-broken]), properties, and values.
** Methodology: if we can document, determine, or hear of (e.g. from web designers/developers) <strong>real world public web use cases</strong> for any particular -moz- innovation, then we should consider pursuing standardization of it. Otherwise, it's better to not standardize so we can change our implementation as needed to match our internal needs (e.g. for UI/themes etc.).
* Previously: Mozilla contractor 2010-146..2011-175
* [http://tools.ietf.org/html/rfc4367#section-3 RFC4367: ASCII art diagram of user client DNS server interaction]
 
== See Also ==
* [[User:Tantek]]
Tantek
Canmove, confirm
2,672
edits
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1134860"

Navigation menu