The future of style
The Future of Style aggregates posts from various blogs that
talk about the development of Cascading Style Sheets (CSS) [not
development with Cascading Style Sheets]. While it is
hosted by the W3C CSS
Working Group, the content of the individual entries represent
only the opinion of their respective authors and does not
reflect the position of the CSS Working Group or the
W3C.
Minutes Telecon 2013-01-16
- Discussed F2F logistics; need more topics for agenda
- Discussed interaction of viewport units and scrollbars, and
avoiding relayout in ‘overflow: auto’ case. Need to evaluate use
cases for viewport units to decide whether ‘auto’ should be laid
out as ‘hidden’ or ‘scroll’.
- Discussed issues with Pointer
Events spec. Specific concerns include:
- Spec seems to confuse people as currently-written
- The
touch-action property might be overly-specific
to touch interfaces
- Discussed whether
touch-action property is
necessary.
- Spec should show examples of how
touch-action is
used in an all-declarative use case. (If it is only useful when JS
is invoked, maybe its behavior should likewise be handled by JS,
not by using a declarative property that’s that expects alternate
handling via JS.)
- Discussed CSS
Masking, progress to LC. Issues raised include:
Full
minutes
Minutes Telecon 2013-01-09
- Resolved: Publish new WDs of css3-transitions
and css3-animations
- Resolved: The url() function can be escaped:
update CSS2.1 errata and css3-syntax.
- Resolved: Allow
background-clip
and background-origin to be specified separately in
the background shorthand
- Resolved:
currentColor still
computes to a color when used as a color property
value; clarify css3-color erratum accordingly
- Discussed case-sensitivity issue again.
- Resolved: If animation name repeated, last
instance wins
- Resolved: Not adding time units selectors for
animations for this level
- Resolved: Empty keyframes with positive
duration still “animate” and fire events
Full
minutes
Bert Bos will give a one-day tutorial (in Dutch) on CSS in
U…
CSS3 Text Decoration Last Call for Comments
The CSS Working Group has published a Last Call Working Draft of
CSS Text
Decoration Level 3. Level 3 extends line
decorations (underlines, overlines, and strike-throughs) to add
controls for color,
style,
position,
and continuity.
It also introduces emphasis
marks (traditionally used in East Asian typography), and
text
shadows (which were deferred from Level 2).
Feedback is welcome, especially from people who
work with non-Latin writing systems. The
deadline for comments is 31 January 2013. As
always, please send comments to the (archived)
public mailing list
www-style@w3.org with the spec code
([css-text-decor-3]) and your comment topic in the
subject line. (Alternatively, you can email one of the editors and
ask them to forward your comment.)
CSS3 Cascading and Inheritance WD Updated!
The CSS Working Group has published an updated Working Draft of
CSS Cascading and
Inheritance Level 3. This is the first update to this module
since 2005. In addition to synchronizing the module with CSS2.1, the update proposes a new
all
shorthand for resetting all properties, a CSS-wide default
keyword for rolling back the cascade, and scoped rules
to the cascade. Feedback is welcome, especially on Chapter
4.
As always, please send comments to the (archived)
public mailing list
www-style@w3.org with the spec code
([css3-cascade]) and your comment topic in the subject
line. (Alternatively, you can email one of the editors and ask them
to forward your comment.)
Minutes Telecon 2012-12-19
- Resolved: Rossen Atanassov replaces Alex
Mogilevsky and Phil Cupp as editor of Flexbox and Grid.
- Discussed Flexbox interaction with multicol and writing
mode
- Resolved: Publish Working Draft of CSS Cascade Level 3 to
replace the 7-year old one, mentioning dbaron’s issues about
scoping and defaults.
- Resolved: Spaces are not optional around
and, or, and not keywords in
@supports syntax.
- Resolved: Publish CSS Text Decoration Level
3 Last Call Working Draft with intro from fantasai.
- Resolved: Daniel Glazman is our new liaison
with EPUB.
- Discussed Animations issues:
- whether
animation-play-state in shorthand
- animations starting in descendant when no longer
display:
none
- what counts as a valid keyframe
- Resolved: Put
animation-play-state back into the
animation shorthand, and let the shorthand reset it if
not mentioned.
Full
minutes
The CSS WG issued a last call for comments for CSS Text
Deco…
Penguin Mark: Blazing Fast Holiday Fun
We don’t want the holiday season to pass without sharing
another
new HTML5 experience that makes the most of your PC hardware and
the new touch capabilities in Windows 8.
Check out Penguin
Mark and enjoy some GPU-powered holiday fun. This experience
brings together hardware-accelerated HTML5 capabilities like
canvas, CSS3 animations and transitions, audio, WOFF, power and
performance APIs, and more. Be sure to turn your volume up for
maximum entertainment. The faster your browser, the higher your
Penguin Mark score goes.
Click to test your browser’s holiday spirit with Penguin
Mark
With Windows 8, we delivered a whole new browserthat’s fast and
fluid, and built for touch browsing. IE10 adds support for a broad
range of developer
capabilities, including
new touch APIs, performance, HTML5, CSS3, JavaScript, and
more. We continue to be amazed and delighted by what developers
are building on HTML5 and excited to be part of it.
Thank you!
Your participation and feedback is an important part of how we
build IE. Today we want to say thank you to everyone who
browses the Web with Windows
8, is using IE9 or
IE10 preview on Windows 7, runs the test drives, and shares
your feedback with the IE team. We also want to thank the people
and groups who make the standards process work, the broad community
of Web developers, and enthusiastic consumers who work to move the
Web forward.
From the entire IE team, we wish you a Happy
Hardware-accelerated Holiday Season, and we look forward
to another exciting year and more progress on the Web in 2013.
—Rob Mauceri, Group Program Manager, Internet Explorer
CSS3 Writing Modes Was Updated
Forgot to announce that CSS Working Group has published an
updated Working Draft of CSS Writing Modes Level
3 back in November. CSS Writing Modes Level 3 defines CSS
support for various international writing modes, such as
left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or
Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical
(e.g. Asian scripts).
We’re hoping this is the last round before Last Call, but to get
there we need your help! Please review the draft and give us
feedback. Changes since the last Working Draft are listed in the
Changes section. Sections that particularly need review and
feedback include
logical directions,
orthogonal flows, and
tate-chu-yoko.
As always, please send feedback to the (archived)
public mailing list
www-style@w3.org with the spec code
([css3-writing-modes]) and your comment topic in the
subject line. (Alternatively, you can email one of the editors and
ask them to forward your comment.)
CSS Fonts Level 3 Updated
Just a quick note to announce that a new working
draft of the CSS3
Fonts spec was published this week.
Significant changes/additions include:
As always, please post any and all comments, preferably
well-reasoned, insightful ones, to (archived)
public mailing list
www-style@w3.org with the spec code ([css3-fonts])
and your comment topic in the subject line.
CSS3 Conditional Rules (@supports) Last Call
The CSS Working Group has published a Last Call Working Draft of
CSS3 Conditional
Rules. This module defines the existing @media rule for
media-specific parts of style sheets, which use media queries as a
condition syntax, and introduces the new @supports
rule for parts of style sheets that are specific to implementations
that support particular property:value pairs. It also
defines associated APIs.
This is a Last Call Working Draft; the working group hopes to
advance this module to Candidate Recommendation soon after the last
call period ends on January 10. If there’s anything you
believe
needs to be changed anywhere in the specification, you should say
so now. Changes since the last Working Draft are listed in the
Changes
section.
As always, please send feedback to the (archived)
public mailing list
www-style@w3.org with the spec code
(>>[css3-conditional]<<) and your comment
topic in the subject line. (Alternatively, you can email the editor
and ask him to forward your comment.)
Minutes Telecon 2012-12-05
- Discussed February F2F logistics.
- Objection to publishing CSS3 Text LC before next F2F.
- Resolved: Publish CSS3 Fonts WD
- Resolved: No exceptional zeroing of negative
margins for flex items.
- Resolved: Min/max clamping step of resolving
flexible lengths does not pass cross-size limits through aspect
ratio into main size flex computations.
- Various Flexbox clarifications reviewed:
Set A,
Set B,
Set C.
- Issue on handling aspect ratio during main size computations
still being worked out. See thread
and
proposed changes.
- Discussed case-sensitivity of CSS identifiers.
Internationalization Working Group recommends Unicode case-folding.
Anne van Kesteren recommends ASCII-folding. Points brought up:
- Some implementations seem to do some form of Unicode
case-insensitivity for class name matching. Some do
ASCII-only.
- HTML spec requires ASCII-folding only for its
case-insensitivity.
- ASCII-folding is easier to implement correctly.
- ASCII-folding is really weird for non-English languages with
case.
- Previous uses of case-insensitivity were ASCII-only idents,
where this wasn’t a usability issue.
No conclusions yet.
Full
minutes
Minutes Telecon 2012-12-12
- Discussed Flexbox issue
wrt stretch-sizing elements with aspect ratio.
- Discussed Animations terminology for Bug
16116.
- Resolved: Transitions defines the timing
functions, Animations has normative dependency on Transitions for
them. (Bug
14784)
- Resolved: Animations only “run” (fire start
events, etc) if they have at least one valid keyframe. (Bug
15251)
- Resolved: When an element changes from
display:none to display:
<non-none>, animations start immediately. (Bug
14785)
- Resolved: An initially-paused animation is
still started (fires start events, etc.) (Bug
14774)
- Resolved: Animations can be paused during
their delay phase, which freezes the remaining delay to be applied
after it unpauses. (Bug
14774)
- Resolved:
animation-play-state is
not in the shorthand on purpose (Bug
14787)
- Resolved:
animation-play-state
has the same list behavior as the other animation properties:
matching the length of animation-name. (Bug
14786)
- Resolved: Look into “adjacent keyframes” for
level 4, but not for the current level. (Bug
20092
– Discussed motivations and problems with Florian’s media query
proposal, along with conceptual framework for extending Media
Queries in level 4.
Full
minutes
Minutes Telecon 2012-11-28
- Discussed allowing background-clip and background-origin to be
separated from each other in the ‘background’ shorthand. (See
issue.)
- Plan to take CSS3 Text / Text Decoration to LC next week unless
there are reasons to hold back.
- Discussed FXTF telecon times and attendance
- Resolved: Viewport units are relative to the
first page’s size only.
- Discussed CR exit criteria and one person writing multiple
implementations
Full
minutes
César Acebal put a new version of ALMcss3, a JavaScript
impl…
6 Dec 2012 César Acebal put a
new version of
ALMcss3, a JavaScript
implementation of the
CSS Template Layout Module,
on github.com. It implements the latest proposed syntax for that
specification.
Native CSS feature detection via the @supports rule
We have practised feature detection to allow us to provide
appropriate code to browsers with differing levels of standards
support for a while now, but we've always needed 3rd party
libraries to handle it. But not for much longer: The CSS3
Conditional Rules Module Level 3 provides the @supports at-rule and
associated JavaScript API, providing a native mechanism for doing
CSS feature detection. In this article we'll give you the lowdown
on how this rule works, looking at a real example in the
process.
Minutes Telecon 2012-11-14
- Resolved: Lea Verou as co-editor for
Backgrounds 4.
- Resolved: Add Simon Sapin as co-editor for
Paged Media 3.
- Discussed handling of low-priority specs.
- Resolved: Add stretch keywords to font
shorthand per jdaggett’s
message.
- Resolved: Use the Editor’s draft version of
rules for font selection wrt glyphs within a family vs. particular
font variant per jdaggett’s
message.
- Resolved: Change
@font-feature-values syntax to use variant
B with @-sign in front of feature types per dbaron’s
message.
- Discussed February F2F logistics: aiming for Feb 5-7 in Tucson,
AZ
Full
minutes
Minutes TPAC 2012 Part VII: Display Models and
Miscellaneous
text-overflow: ellipsis
- Resolved: Selecting the ellipsis selects the
ellipsed text.
- Resolved: If all of ellipsed text is selected,
show selection of ellipsis.
- Resolved: Put a note that behavior wrt
partially-selected text is up to UA
- Discussed clarifying examples in spec, adding tests.
Full
minutes
Grid Layout
Brief discussion of direction, progress, and lack thereof.
Full
minutes
HTML5 Challenges
- Resolved: Add
display: svg and
display: math or something similar at some point.
- Resolved: Toggleable states is a cool idea and
work on it at some undetermined but not high priority. See Tab’s post for a discussion of
some ideas and problems with them.
- Discussed
<iframe seamless>; CSS object
negotiation algo needs an update to handle it.
Full
minutes
Display Models
- Discussed splitting
display into multiple
properties, particularly whether to split inner and outer display
models into separate properties
(display-inside/display-outside).
- Discussed discarding boxes vs. hiding them.
- Resolved: Start
css-display-3
as a new ED.
Full
minutes
Minutes TPAC 2012 Part VI: Style Attributes, Conditional Rules,
Cascade, Case-sensitivity
Style Attributes
- Reviewed test failures: various parsing bugs and some trouble
handling
xml:base.
- Plan to move to REC: get two implementations that parse
conformantly, mark
xml:base test out-of-scope.
Full
minutes
CSS3 Conditional Rules
- Reviewed outstanding issues/edits
- Resolved: Publish CSS3 Conditional Rules
as LCWD on Tuesday unless dbaron objects within next few days.
Full minutes: Part
I, Part
II
CSS3 Cascade
- Resolved: Drop alternate style sheet syntax
from @import in css3-cascade.
- Resolved: Tab and fantasai to take over
css3-cascade.
- Plan going forward is:
- Remove alternate style sheets syntax
- Synchronize text with CSS 2.1 and make sure corrections all
copied over
- Editorial reorganization of spec to make sure it still makes
sense
- Add cascading rules for scoped styles, the ‘all’ shorthand, and
the ‘default’ keyword
Full
minutes
Case-sensitivity of CSS identifiers
Some discussion with Internationalization WG. No conclusions,
but field of options seems to have narrowed to either
ASCII-insensitivity or Unicode case-folding.
Full
minutes
Minutes TPAC 2012 Part V: Masking, Compositing, Transforms,
Transitions, Animations
Masking
- Resolved: Add “no clipping” value to
mask-clip
- Resolved: Deprecate
clip,
recommend clip-path from now on.
- Resolved: Add
inset() or
inset-rectangle() to the Shapes module.
- Discussed percentage sizing reference.
- Discussed interpretation of fragment URLs against SVG.
- Resolved: Publish FPWD Masking as
css-mask
Full
minutes
Compositing
- Resolved: Turn the Compositing default to be
isolated groups.
Full
minutes
Transforms
- Resolved: Accept Aryeh’s
proposal regarding transform parents, exact wording TBD.
- Bug
15605 (w-parameter for perspective) needs review from
implementers.
- Discussed 2D interpolation methods for transitioning
transforms.
- Brief discussion of stereo vision
Full minutes: Part
I, Part
II
Animations
- Discussed snapshotting vs. dynamic modification of animation
parameters.
- Resolved: Change the animation properties to
be dynamically changeable, details TBD.
- Resolved:
@keyframes can be
dynamically changed
- Resolved: Copy over the pseudo-element info
from transition events to animation events.
- Resolved:
animation-name‘s length
is authoritative. Other animations properties are adjusted to its
length.
- Resolved: When you encounter duplicate
animations names, last one wins.
- Resolved: Make animations transition
all properties. Unless otherwise specified, discrete properties
take their starting values below 50% timing function progress, and
end values above 50% timing function progress.
- Discussed interaction of simultaneous transitions and
animations, particularly how that fits with the cascade.
Full minutes: Part
I, Part
II
Transitions
- Resolved: Clarify that none, inherit, and
initial are not allowed at any position within the list for
‘transition-property’; such a declaration is syntactically
invalid
- Resolved: Animations of colors are in
pre-multiplied space.
Full
minutes
Minutes TPAC 2012 Part IV: Paged Media, Fragmentation,
Regions
Paged Media
- Current variable-size margin box calculation rules are
quadratic; Simon Sapin has a better proposal, which will be
incorporated into the spec.
- Discussed concept of “initial containing block”, which is used
for various things, and needs to be clarified wrt fragmented
layouts.http://lists.w3.org/Archives/Public/www-style/2012Nov/0246.html
- Resolved: Add
:blank
@page selector to CSS3 Paged Media.
Full
minutes
CSS Fragmentation
- Discussed fragmenting into too-small and zero-height
fragmentation containers. No conclusions. Need a concrete
proposal
- Resolved: Relpos happens after
fragmentation
- Filed issue on clarifying how positioning coordinates cross
pages.
Full
minutes
Overflow Regions
Tab proposed focusing on the overflow method of region
auto-generation, instead of working on making random elements
become regions containing randomly-spliced flows. Arguments in
favor were that it solves the junk-elements-in-document problem,
and that the enforced one-to-siblings relationship of the
overflow-regions model avoids crash-prone complexity in the layout
engine. Alan countered that it can’t handle all the use cases.
There was some dispute about to what extent this was true. Rossen
also requested that programmability of region containers not be
ignored as a requirement.
Full
minutes
Regions
- Resolved: Close Bug 15186
in Regions, concerning handling arbitrary amounts of content in a
region chain.
- Resolved: Bug 15824
– keep the current spec text, where regions all create stacking
contexts for the stuff flowed into them.
- Discussed issue of elements becoming regions; agreed to leave
it open.
- Resolved: Need to split the concept of
“initial containing block” into two parts, as necessary for the
different things the ICB is currently used for.
Full
minutes
Minutes TPAC 2012 Part III: Collisions, Exclusions, Line
Layout, and Box/Alignment
CSS Collision
- Florian requested feedback, whether to place on
dev.w3.org.
- Discussed marking certain editor’s drafts as thought
experiments that are not intended for implementation.
Full
minutes
Exclusions
- Resolved: Bug 15085
closed, keep the wrap-through property
- Resolved: Bug 15087
closed, interaction of floats and exclusions is now explained in
the spec section 3.6.
- Discussed Bug 15089,
making e.g. circle fit content
- Resolved: Bug 15083
closed as processing model is now described. Still some concerns
remaining wrt allowing an implementation to calculate correct
results.
Full
minutes
Line Layout Module
- Steve reviewed progress on overhauling the Line Layout module.
(It’s still mostly a mess.)
Full
minutes
CSS3 Box Module
- Discussed various approaches for alignment in block
layout.
Full
minutes
Minutes TPAC 2012 Part II: Text, Writing Modes, and Sizing
Writing Modes
- Resolved: Defer to level 4 the
text-combine-mode property, and all values for
text-combine-horizontal except none and
all.
- Resolved: Publish a new WD of Writing Modes when
UTC releases a new UTR-50 report, or Nov 15, whichever comes
first.
Full
minutes
Text and Text Decoration
Full
minutes
Abstract Directional Terminology
- Resolved: Revert block-axis directions
head/foot back to before/after (revert earlier decision); WG may
however consider other terms.
- Resolved: Use over/under terms instead of
above/below for
text-underline-position,
text-emphasis-position, consistent with
text-decoration (overline vs.
underline).
Full
minutes
CSS3 Sizing
Full
minutes
Multi-column Layout
Discussed rules for sizing under the case labelled
available-width == unknown, what that means, and
whether various parts of the sizing pseudo-algorithm should be
removed. No conclusion.
Full
minutes
Minutes TPAC 2012 Part I: Administrative, Prioritization, and
HTMLWG
Spec Shortnames
- Assigned actions for next steps in switching over all
specs.
Full
minutes
Prioritization
- Co-chairs surveyed WG members about their priorities; results
are
posted by glazou with VSI = Very Strong Interest, SI = Strong
Interest, LI = Low Interest, NI = No Interest.
- Top items are Flexbox, Transforms, Transitions, Animations, and Conditional Rules,
regardless of formula.
- Layout modules (Flexbox, Multicol, Regions, Grid) always in top
ten
- Middle shifts around depending on weighting formula, but Level
4 specs consistently towards the bottom of the list
Full
minutes
HTMLWG/CSSWG Coordination
Identified several places where coordination is needed:
- Selectors. This is largely handled due to last year’s Selectors 4 FPWD, and
subsequent edits that aligned the HTML spec with that.
- Scoped style sheets. Various aspects of this are either
underdefined or incorrectly specced. Several CSSWG members
recommended to drop it from the HTML5.0 timeline. Aside from the
HTML syntax for invoking scoped styles, many things need to be
defined that belong on the CSS side, specifically:
- Handling of scoped selectors (mostly handled in latest
Selectors 4)
- Potentially, CSS syntax for changing how selectors are
scoped.
- Scoping the cascade (will be drafted into CSS3 Cascade soon, but no
draft yet exists as of TPAC 2012)
- Handling of various globally-scoped at-rules such as
@font-face.
The third issue was about communication. Historically, the
HTMLWG has put things in their spec that affect the interpretation
of CSS (or, in some cases, extend CSS) without notifying the CSSWG
of such changes or additions, giving the CSSWG no opportunity to
review and send feedback or to incorporate such changes into its
own specs. The HTMLWG countered that the CSSWG should file bugs
about things that are wrong (once they find out about them) and
escalate things using the HTMLWG process.
Present in this discussion were the CSSWG, two of the HTMLWG
co-chairs, one of the HTML5 editors, and W3C’s Philippe Le
Hégaret.
Full
minutes
A new Working Draft: CSS Masking; and an updated Working
Dra…
Updated CSS3 Text; split out CSS3 Text Decoration
he CSS WG has published an updated Working Draft of CSS Text Level 3 and a first
public Working Draft of CSS Text Decoration Level
3, which was split out from the previous CSS3 Text draft.
CSS3 Text covers
various aspects of text layout including white space
processing, text
transformations, line breaking,
justification,
and indentation.
Significant changes since the previous WD are listed in the
Changes
section.
CSS3 Text
Decoration covers text decoration: the various line
decoration options as well as CJK-style emphasis
dots and text
shadows. Significant changes since the previous WD are listed
in the Changes
section.
Both drafts include many additions to CSS2 to address
internationalization concerns, allowing better typography in
non-Western (and Western) scripts.
Since there are no significant, known open issues, Koji and
fantasai are planning for the next draft to be a Last Call Working
Draft to be published in December, and have requested review from
the CSSWG accordingly. We would also appreciate reviews from anyone
else who has an interest in text layout or CSS
internationalization.
As always, please send feedback to the (archived)
public mailing list
www-style@w3.org with the spec code ([css3-text]
or ) and your comment topic in the subject line. (Alternatively,
you can email one of the editors and ask them to forward your
comment.)
IE10: Fast, Fluid, Perfect for Touch, and Available Now for
Windows 7
In Windows 8, we reimagined the browser with IE10. We designed
and built IE10 to be the best way to experience the Web on Windows.
With the IE10 Release Preview for Windows 7 consumers can now enjoy
a fast and fluid Web with the updated IE10 engine on their Windows
7 devices. The release preview of IE10 on Windows 7 is
available for download today.
IE10 on Windows 8 brings an entirely new browsing experience and
set of capabilities to the Web, such as a new touch first browsing
experience and
full screen UI for your sites, security improvements that offer
the
best protection against the most common threats on the Web,
improved performance, and support for the HTML5 and CSS3 standards
developers need.
With this release preview, Windows 7 customers receive all of
the performance, security, and under-hood changes that enable a
stellar Web experience. IE10 Release Preview also sends the "Do Not
Track" signal to Web sites by default to help consumers protect
their privacy.
Fast and Fluid
Browser performance is critical for running today’s modern Web
sites and applications. IE10 is all around fast, bringing improved
hardware acceleration and
Chakra JavaScript engine to Windows 7. We continue to focus on
improving real world site performance and
third party recognition of IE's leadership in this area has
been consistent.
You can experience IE10’s leading performance first hand with
new demos on the IE Test Drive
site with examples of hardware accelerated rendering in the
Aston
Martin 3D visualization for high frame rates, and
interactivity, touch, and media with Audio
Explosion.
The
Mandelbrot test drive is another example of how IE10 runs real
world sites fast, particularly sites with computationally intensive
JavaScript and graphics. In this demo you can drill into detailed
views of the Mandelbrot set and see how long it takes to calculate
the view and how many iterations are calculated per second.
This image shows one of the presets calculated using the
Mandelbrot Explorer test drive demo.
The chart below shows the result of Mandelbrot calculations for
21 presets run in IE10, Chrome 23, and Firefox 16, showing IE10 on
average is over twice as fast as Chrome and about 20% faster than
Firefox. Each calculation was run on identical hardware, a single
Samsung Series 9 laptop with an Intel® Core™ i5-2537M CPU @ 1.40
Ghz with 4GB of memory running 64-bit Windows 7. You can see the
full data results from this comparison
here.
This chart shows the results of 21 Mandelbrot preset
calculations run in IE10, Chrome 23, and Firefox 16 on Samsung
Series 9 laptop with an Intel® Core™ i5-2537M CPU @ 1.40 Ghz with
4GB of memory running 64-bit Windows 7
More Interoperable HTML5 Support
IE10 shines on Windows 8, and with this release preview, IE10
brings the same powerful HTML5 engine to Windows 7 customers:
Rich Visual Effects: CSS Text Shadow, CSS 3D
Transforms, CSS3 Transitions and Animations, CSS3 Gradient, SVG
Filter Effects
Sophisticated Page Layouts: CSS3 for
publication quality page layouts and application UI (CSS3 grid,
flexbox, multi-column, positioned floats, regions, and
hyphenation), HTML5 Forms, input controls, and validation
Enhanced Web Programming Model: Better offline
applications through local storage with IndexedDB and the HTML5
Application Cache; Web Sockets, HTML5 History, Async scripts, HTML5
File APIs, HTML5 Drag-drop, HTML5 Sandboxing, Web workers, ES5
Strict mode support.
Developers building on these capabilities in Windows 8 can run
the same markup with the same performance and capabilities on
Windows 7. You can find a full list of new functionality available
to developers in the IE10 developer guide here.
Commitment to Privacy with "Do Not Track" on By
Default
IE10 continues our focus on helping consumers protect their
privacy, which started in IE9 with features such as Tracking
Protection. In Windows 8, "Do Not Track" (DNT) is "on" in the
Express Settings at time of set-up, and IE10 in Windows 7 also
sends a "Do Not Track" signal to Web sites by default. Microsoft's
customers
have been clear that they want more control over how their
personal information is used online. While "Do Not Track" is
a technology solution that’s still in its formative stages, it
holds the promise of giving people greater choice and control of
their privacy as they browse the Web. IE10 Windows 7
customers are notified of the "Do Not Track" setting via IE10's
first run welcome page, including instructions for how they can
turn off "Do Not Track" should they wish.
We believe that meeting customer expectations by putting people
first is the best way to grow online commerce and the Internet
economy. Our commitment is to provide Windows customers an
experience that is "private by default" in an era when so much user
data is collected online. IE10 is the first browser to send a "Do
Not Track" (DNT) signal by default.
A Better Web Today, and Ahead
The opportunities continue for HTML5 to make both Web sites and
applications better. Those opportunities are exciting for everyone
on the Web.
IE10 is an entirely new IE. It's fast, fluid and perfect for
touch. Try it out for yourself on a Windows 8 device or, if you are
a Windows 7 user,
download the preview today. We look forward to continued
engagement with the developer community and your feedback on
Connect.
-- Rob Mauceri, Group Program Manager, Internet Explorer
A new Working Draft: CSS Text Decoration Module Level 3;
and…
Chinese Developers endeavor to get more involved in the
community - Test The Web Forward hackathon in China
W3C China Office and Adobe co-organized the Test The Web
Forward event on Oct 20-21, 2012 in Beijing. The intention of
this hackathon was to help more Chinese developers to get involved
in contributing to the web platform. Three W3C specifications
including CSS Flexible Box, CSSOM View, and CSS3 Backgrounds and
Borders were targeted during this event. 17 experts from W3C,
Adobe, Google, Intel, Mozilla, Opera, UCWeb, Tencent, Baidu,
Taobao, Qihoo360, Maxthon, and Huawei were there to help the
attendee to get acquainted with how to Read a W3C Spec, how to
Write a W3C Reftest and how to File a Good Bug Report. Over 260
developers from about 160 organizations registered for this event.
119 test cases (hard: 1, normal: 9, easy: 109) were submitted and
12 browser bugs were filed as the results of the test hackathon.
Positive feedbacks have been gained from local developer
communities and the industry. And the enthusiasm to continue the
efforts of Test The Web Forward event next year in China is under
discussion and more local industry volunteers to participate and
contribute.
Details about the browser bugs that have been filed druing the
event:
- CSSOM View
-
- Firefox Bug 803950 - matchMedia addListener event cannot be
triggered every time by width be change over the condition.
- Not yet logged into bug system] Opera alpha channel bug
- CSS3 Backgrounds and Borders
-
- WebKit Bug 99922 - [css border] border-image doesn't honor
broder-style
- WebKit Bug 99926 - Should show complete tiles when set
'border-image-repeat' as round
- WebKit Bug 99927 - transform3d conflict with background
animation
- WebKit Bug 99928 - [CSS] shadow from radius has wrong render in
webkit
- Firefox Bug 803947 - [css border-radius] replaced element set
border-radius will contents overflow.
- [Not yet logged into bug system] IE Bug: When IE9 table's
border is set to collapse, border-radius is not ignored.
- CSS Flexible Box
-
- WebKit Bug 99923 - margin-top/bottom has no effect for child
nodes of flex items
- WebKit Bug 99924 - WebKit does not support 'flex-wrap:
nowrap'
- WebKit Bug 99925 - Setting width of a flexitem causes the
adjacent flex item to be displayed poorly.
- [Not yet logged into bug system] Bug: Flexible Box Override
child display property and set them to display:block
Updated Working Draft: CSS Grid Layout
Feeds
The Future of Style features:
If you have a post you want to add to this feed, post a link (or
the whole thing) on the CSS3
Soapbox. If you own a blog with frequent posts about the future
of CSS, and want to be added to this aggregator, please get in
touch with fantasai.
