text:
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.
:matches() to
inside a
:not() is the specificity of the most
:active on
:focus-within that
matches on the same things as
:focus, plus parents,
including if there are Shadow DOMs
:hover and
:active should propagate from the labeled control to
the label, in addition to the other direction.
text-overflow, the conversation about handling
items where, due to other properties, the text can't overflow ended
up being too complex for the time on the telecon and will go back
to the mailing list.
flex-basis: auto changes (auto means
main-size and add a keyword for automatic sizing)
urange (available
here) could move to the Fonts spec. There was
disagreement between jdaggett and TabAtkins as to if this
additional normative text was necessary for the spec, however,
implementers stated that they did want the text available to them.
A compromise was reached where it would be in an appendix so that
regular authors wouldn't normally encounter it.
urange definition to an
appendix in the Fonts spec.
content: icon and the icon
property from CSS-UI
nav-index from level 3 of CSS-UI and put it
on a wiki
nav-index to the wiki here.
issue, so discussion will continue on the mailing list.
If you use my Unicode character pickers, you may have noticed some changes recently. I've moved several pickers on to version 14. Most of the noticeable changes are in the location and styling of elements on the UI – the features remain pretty much unchanged.
Pages have acquired a header at the top (which is typically hidden), that provides links to related pages, and integrates the style into that of the rest of the site. What you don't see is a large effort to tidy the code base and style sheets.
So far, I have changed the following: Arabic block, Armenian, Balinese, Bengali, Khmer, IPA, Lao, Mongolian, Myanmar, and Tibetan.
I will convert more as and when I get time.
However, in parallel, I have already made a start on version 15, which is a significant rewrite. Gone are the graphics, to be replaced by characters and webfonts. This makes a huge improvement to the loading time of the page. I'm also hoping to introduce more automated transcription methods, and simpler shape matching approaches.
Some of the pickers I already upgraded to version 14 have mechanisms for transcription and shape-based identification that took a huge effort to create, and will take a substantial effort to upgrade to version 15. So they may stay as they are for a while. However, easier to handle and new pickers will move to the new format.
Actually, I already made a start with Gurmukhi v15, which yanks that picker out of the stone-age and into the future. There's also a new picker for the Uighur language that uses v15 technology. I'll write separate blogs about those.
[By the way, if you are viewing the pickers on a mobile device such as an iPad, don't forget to turn Autofocus off (click on 'more controls' to find the switch). This will stop the onscreen keyboard popping up, annoyingly, each time you try to tap on a character.]
::grammar-error and
::spelling-error, including information pertaining to
the security concerns.
content property should stay where it is.
:hover pseudo was wrong and
will be changed.
::selection should inherit
Today we are rolling out a new Windows 10 preview build with significant Internet Explorer interoperability updates. In line with our commitment to interoperability and compatibility, this update includes over 2000 fixes for interoperability issues, support for 20 new platform features, and our new architecture for advancing interoperability and compatibility. We're excited to be sharing this work at such an early stage in our development process and we look forward to hearing your feedback. We're also rolling out this preview build to users of our new RemoteIE service, available for Windows, Mac OS X, and other platforms.
The cornerstone of this update to IE is the "Edge" mode platform—a new document mode designed with interoperability at its core. With this mode, we're applying the highly successful interoperability strategy of Windows Phone 8.1 Update to Windows 10.
As we announced in August 2013, we are deprecating document modes as of IE11. With our latest platform updates, the need for legacy document modes is primarily limited to Enterprise legacy web apps. With new architectural changes, these legacy document modes will be isolated from changes in the "living" Edge mode, which will help to guarantee a much higher level of compatibility for customers who depend on those modes and help us move even faster on improvements in Edge. The next major version of IE will still honor document modes served by intranet sites, sites on the Compatibility View list, and when used with Enterprise Mode only.
Public Internet sites will be rendered with the new Edge mode platform (ignoring X-UA-Compatible). It is our goal that Edge is the "living" document mode from here out and no further document modes will be introduced going forward. We need your help in testing this new mode so we are enabling it on by default for a small percentage of the Windows Insider user base and those of you that manually select the mode (see below).
Edge mode introduces an interoperable UA string designed to get today's modern Web content, and to avoid old IE-only content. We've also spent a lot of time ensuring that the IE platform behaves like modern Web content expects.
In cases where these changes necessarily differ from standards, we're following through with standards bodies and other browsers to update specs and implementations to reflect the interoperable behavior.
Also in Edge mode are early implementations of several in development features (we'll blog more about these in depth soon):
CSS Preserve-3D – A popular developer request, this feature enables CSS transforms on multiple elements to be composed as a part of a 3D scene rather than flattened together.
Content Security Policy 1.0 – CSP is the next step forward since HTML5 Sandbox in preventing cross-site scripting. Pages provide a policy via the Content-Security-Policy header. This policy defines the origins from which resources on the page (JS, CSS, plugins, images, etc) are allowed to be loaded. This adds a defense-in-depth mechanism for preventing malicious content from being injected into the page. Resources blocked by CSP are reported through F12 tools and, optionally, as a report back to the server.
CSS Interaction Media Queries (Level 4) – A key component in responsive design is responsive input handling. We've talked before about adapting UX for input types, and this feature gives Web developers a new tool to do just that. Stylesheets can now use pointer and hover media queries to adapt UI based on the general precision of the user's input (fine/coarse) and whether the device supports hover.
Gamepad API – First previewed earlier this year, Gamepad API is now in the preview for Windows 10. Plug in an Xbox One or Xbox 360 controller and check out our demo code on GitHub.
WAV Audio – This audio format uses PCM audio for lossless quality. With this release, WAV is supported in the <audio> element and will eventually be supported with Web Audio in a future release.
Selection API– We've improved our interoperability for the Selection object by implementing APIs like Selection.extend(), containsNode(),and setBaseAndExtent(). We have also helped get the W3C Selection API specification to First Public Working Draft and ensured it covers all of these interoperable APIs.
ECMAScript 6 Features – New language features from the latest ES6 "Harmony" draft specification:
Classes – syntax for declaring classes in ES6.
Promises – allows easier and cleaner asynchronous coding. Adds the Promise constructor, along with the 'all' and 'race' utility methods to the language itself.
Iterators – enables iteration over iterable objects (including arrays, array-like objects, iterators and generators), invoking a custom iteration hook with statements to be executed for the value of each distinct property.
Arrow Function – the arrow (=>) provides a shorthand for the function keyword with lexical 'this' binding.
Math, Number, Object, String Built-ins – dozens of new utility functions and properties for manipulating and inspecting data.
Object Literal Enhancements – adds computed properties, concise method definitions, and short-hand for properties whose value is initialized to a same-named variable.
Spread – the spread operator expands iterable expressions into individual arguments. For example, a.b(…array) is roughly the same as a.b.apply(a, array).
Template Strings – string literals that allow for expressions to be evaluated and concatenated with the string literal.
Symbols – allows properties to be added to existing objects without the possibility of interference with the existing properties, unintended visibility, or with other uncoordinated additions by any other code.
Weak Set – a set of objects such that those objects will be collected if they are not referenced anywhere else.
Also in this release is the introduction of a new experimental features dashboard, accessed by browsing to about:flags. Here you'll find new platform experiments that you can enable to try out the very bleeding edge of what we're working on. Future experiments may include new standards we're working on, interoperability fixes we're trying out, new performance or security architectures, and more.
Given the sheer volume of changes in Edge mode, we're going to progressively roll out the new mode by choosing a random set of Windows Insiders to get Edge while the rest remain in 11 document mode. Our data science and quality engineering teams will leverage user feedback and anonymous telemetry to guide the roll out while we make tweaks to the platform in future preview builds accordingly.
If you're a developer coding against new features or testing for compatibility, you can head over to about:flags and choose Edge mode explicitly by setting "Enable Experimental Web Platform Features" to "Enabled" ("Automatic" restores you to the default roll out and "Disabled" lets you compare with 11 mode).
At any time, developers can identify the mode a page is in via F12 tools. Note that dynamically switching between Edge and other document modes from F12 isn't yet supported (we told you these experiments may bite!). For now, use about:flags for switching when developing and testing.
We're sharing our changes earlier in the process than ever so we can collect your feedback to help shape the product. Last month, we introduced the IE Platform Suggestion Box on UserVoice where developers can suggest and vote on improvements to the platform. In this release, we're adding a feedback tool right in the top-level UI. Just click the smiley face icon to "send a frown" such as reporting a problem on a site. If the page is running in Edge mode, you can also try reloading in the "compatibility mode" (IE11 behavior). As always, you can also report issues through Connect or the Windows Feedback app in the Windows 10 Tech Preview.
We're excited to share with you an early look at what we've been working on. Join our engineering team on Twitter at 11am PST Friday November 14 where we'll be answering your #AskIE questions, and follow along with some of the other work we're planning at status.modern.IE.
Jacob Rossi (@jacobrossi) - Senior Program Manager, Internet Explorer
Update 11/12/2014 : Added ES6 Proxies and WeakSet to the list of features in this preview build, removed RegExp built-ins (still in development)
@keyframe rules except the animation timing function
(where we have explainer text already)
names and will throw an error when set through the OM
findRule/deleteRule return/delete
the last rule with the specified key.
auto/main-size issue.
Last March I pulled together some notes about the Tibetan script overall, and detailed notes about Unicode characters used in Tibetan.
I am writing these pages as I explore the Tibetan script as used for the Tibetan language. They may be updated from time to time and should not be considered authoritative. Basically I am mostly simplifying, combining, streamlining and arranging the text from the sources listed at the bottom of the page.
The first half of the script notes page describes how Unicode characters are used to write Tibetan. The second half looks at text layout in Tibetan (eg. line-breaking, justification, emphasis, punctuation, etc.)
The character notes page lists all the characters in the Unicode Tibetan block, and provides specific usage notes for many of them per their use for writing the Tibetan language.
See the Tibetan Character Notes
Tibetan is an abugida, ie. consonants carry an inherent vowel sound that is overridden using vowel signs. Text runs from left to right.
There are various different Tibetan scripts, of two basic types: དབུ་ཙན་ dbu-can, pronounced /uchen/ (with a head), and དབུ་མེད་ dbu-med, pronounced /ume/ (headless). This page concentrates on the former. Pronunciations are based on the central, Lhasa dialect.
The pronunciation of Tibetan words is typically much simpler than the orthography, which involves patterns of consonants. These reduce ambiguity and can affect pronunciation and tone. In the notes I try to explain how that works, in an approachable way (though it's still a little complicated, at first).
Traditional Tibetan text was written on pechas (དཔེ་ཆ་ dpe-cha), loose-leaf sheets. Some of the characters used and formatting approaches are different in books and pechas.
For similar notes on other scripts, see my docs list.
initial-letter section intact, and 2 prior sections
pointing to appropriate parts of 2.1, with note that they will be
initial-letter depends on line
grid spacing or (if none) line-height of containing block. Does not
depend on content of the lines.
initial-letter does not have
number. Alignment point
is determined by script.
initial-letter was also an
area of concern.
Full Minutes || Spec Referenced
start/end events fire with 0
Full Minutes || Spec Referenced
Full Minutes || Specs Referenced: GCPM3 and GCPM4
image() function is undergoing edits for Image Level 3
Full Minutes || Spec Referenced
calc() of Keywords
calc(), which presents behavioral complications for
many keywords.
calc() doesn't have min/max
functions was re-answered.
Full Minutes || Spec Referenced
motion-position and
motion-rotation and their
Full Minutes || Spec Referenced
device-* media
features. Keep behavior, but authors "must not use"
resolution MQ uses the vertical
resolution when pixels are not square.
none and
Full Minutes || Spec Referenced
display to the next
level; this will allow restricting combinations of
display-inside and
display-outside that
are difficult to implement at this time.
box-suppress, including
details that need to be defined for the
hide value and
how this interacts with
visibility and
speak. This section needs more work.
Full Minutes || Spec Referenced
display: none and the root
Full Minutes || Spec Referenced
Full Minutes || Spec Referenced
caret-color to css3-ui
::selection back
and potential issues with exposing security-sensitive items (such
as spell-check)
::selection to Pseudo-elements 4.
Full Minutes || Spec Referenced
last-visible-line-in-block ellipsis. More discussion
is needed to create a concrete understanding of all the related
problems and come up with a solution.
:focusWithin, can use
:has(:focus) instead.
Full Minutes || Spec Referenced
overflow:scroll boxes
flex-wrap: balance idea
but are deferring it (issue
distribute special-case
logic from
inter-character, same meaning
Full Minutes || Spec Referenced
Opera 25 (based on Chromium 38) for Mac and Windows is out! To find out what's new for consumers, see our Desktop Team blog. Here's what it means for web developers.
HTML element
<picture> is now available in Opera (and
Chrome) by default! This new HTML element can be wrapped around any
good ol'
 element to enable art direction,
different images types, high-DPI images, changing image sizes, and
more. We recommend you read Yoav
Weiss's introduction to native responsive images, or
look at Andreas
Bovens's list of responsive image use cases with documented code
The Screen
Orientation API provides the ability to read the user's screen
orientation type and angle, to be informed when the screen
orientation state changes, and be able to lock the screen
orientation to a specific state. This functionality is available
under the
window.screen.orientation object.
Opera now supports the Notifications API,
available under the
window.Notification object. Even
though the Chromium project has supported this feature for a long
time, we wanted to get the UX right before shipping this in
The way Chromium deals with notifications makes it seem non-native to the operating system on most platforms. We wanted to make it feel native on all our supported platforms, and we worked on it to make it happen. As a result, Opera's web notifications look and behave like native notifications. We believe this is a much better experience for users.
Opera add-ons can make use of this functionality through
chrome.notifications API. Note that because of our
native OS integration, only simple notifications (similar to
non-rich web notifications) are supported in Opera; rich
chrome.notifications are not.
File constructor
The global
File constructor can be used to programmatically
generate file objects on the client side:
var html = '<!DOCTYPE html><title>Test</title>
Hello world!
';
var file = new File([html], 'test.html', {
'type': 'text/html'
Here's a demo that generates files on the client side and offers download links for them.
TextDecoder API
The WHATWG Encoding
Living Standard defines
TextEncoder and
TextDecoder interfaces that make it easy to translate
between raw bytes and native JavaScript strings, regardless of
which of the many standard encodings you need to work with.
// Encode a string using UTF-8:
var encoder = new TextEncoder('utf-8');
var encoded = utf8encoder.encode('foo𝌆bar');
// → an ArrayBuffer containing the bytes for this string as per UTF-8
// → [0x66, 0x6F, 0x6F, 0xF0, 0x9D, 0x8C, 0x86, 0x62, 0x61, 0x72]
// Decode the UTF-8 bytes back into a string:
var decoder = new TextDecoder('utf-8');
// → 'foo𝌆bar'
For more information on this feature, see
ArrayBuffer ↔ string conversion with the
Encoding API.
ECMAScript 6 introduces a new
for-of construct,
iterates over iterable objects like arrays, array-like objects,
strings, iterators, generators, maps, and sets.
var iterable = ['a', 'b', 'c'];
for (var item of iterable) {
My favorite example of this is
iterating over all characters in a string. With
for-of, supplementary Unicode symbols are
automatically treated as a single unit, just like you'd expect. In
ES5 you had to write a lot of boilerplate code to make that
var string = 'foo𝌆bar';
for (var item of string) {
// → 'f', 'o', 'o', '𝌆', 'b', 'a', 'r'
Map object is a simple key/value map. Unlike
regular objects in JavaScript, which store their keys as strings,
Maps accept any value — both primitive values and
objects — as keys and values. Here's a simple example:
var map = new Map();
var person = { 'name': 'John Smith' };
// Store a value in the Map that is tied to this `person` object.
map.set(person, 'foo');
// Later, we can check if the Map contains a matching value:
map.has(person); // true
// That value can be retrieved based on the `person` object:
map.get(person); // 'foo'
// Iterate over the items in the Map using `for-of`.
for (var item of map) {
item[0], // key
item[1] // value
Set object is a collection of unique values.
Sets accept values of any type — both primitive values
and objects.
var set = new Set();
var person = { 'name': 'John Smith' };
// Store some values in the Set.
set.add(42); // Note: duplicates are ignored.
// Later, we can check if the Set contains a value:
set.has(42); // true
set.has(person); // true
// Iterate over the items in the Set using `for-of`.
for (var item of set) {
Symbol is a unique and immutable data type that
allows properties to be added to existing objects without the
possibility of interference with the existing properties,
unintended visibility, or with other uncoordinated additions by any
other code.
Here's an example:
(function() {
var symbol = Symbol();
var object = {};
object[symbol] = 42;
console.log(object[symbol]); // 42
Due to the use of Symbols, it's impossible to extract the
private value
42 from the object unless you
have access to the
symbol reference variable.
Object.getOwnPropertySymbols can be used to
programmatically list the Symbol properties on a given object.
Here's an example that demonstrates that
Array.prototype makes use of Symbols:
// → [Symbol(Symbol.unscopables), Symbol(Symbol.iterator)]
Unscopables allow properties to be hidden from
with statement lookup rules. This makes it possible to
add new properties to existing host objects, both in JavaScript and
in the DOM, without breaking backwards compatibility.
ES6 defines lots of new mathematics-related functions, which we're happy to support in this new release:
<text> elements got
a nice performance boost.
Also, SVG
<feBlend> elements now support the
following additional blend modes (for use in
Only Presto
(i.e. Opera ≤ 12) and WebKit-based browsers ever implemented
support for SVG web fonts in
@font-face. Nowadays WOFF
and WOFF2 are a much better choice.
As of this release, SVG web fonts are no longer supported, except on Windows systems which use GDI-based font rendering instead of DirectWrite-based font rendering (i.e. Windows < 7). Note that although the feature still works on those systems for now, it is considered deprecated, and support will eventually be removed completely.
Opera for Mac is now a 64-bit browser. This offers many benefits for speed, stability and security.
The flip side of this change is that the 32-bit Silverlight plug-in for Mac no longer works, which obviously affects Silverlight-based applications, such as Netflix. At the moment, a 64-bit version of the Silverlight plugin is not available.
Other than Silverlight, Netflix also supports video using Encrypted Media Extensions (EME). However, given that Opera doesn't support EME, this option unfortunately does not work either.
If you're interested in experimenting with features that are in the pipeline for future versions of Opera, we recommend following our Opera Developer stream.
Bringing HTML5 to the status of W3C Recommendation (in October 2014) is a defining moment in the development of the Open Web Platform (OWP), a set of technologies for developing distributed applications with the greatest interoperability in history. This year is also the 25th anniversary of the Web and 20th anniversary of W3C, making this an even more meaningful time to engage with the community about the Next Big Thing for the Web Platform.
My starting point for this discussion is that, now that HTML5 is done, W3C should focus on strengthening the parts of the Open Web Platform that developers most urgently need for success. I call this push for developers "Application Foundations."
This is a new formulation, shaped in part by discussion at the September Extensible Web Summit in Berlin, as well as discussions within the W3C staff. I am planning further discussion at W3C's TPAC 2014 meeting at the end of the month, and I welcome your feedback to this post and in the months ahead.
While this formulation is new, most of the work is not new. Rather, this represents a new way of looking at the considerable work that is already in the Web community, and placing some structure around the considerable work in front of us.
The OWP is widely deployed, improving in function every day, and transforming industry after industry. According to a survey earlier this year, 42% of developers are using HTML5, CSS, and JavaScript when building applications. The promise of the Open Web Platform is to lower the cost of developing powerful applications to reach the most people, on any device.
As popular as the OWP is, it is still too challenging for developers to create some types of Web applications. Lack of broad interoperability for some features complicates development. Lack of standard features in the platform drives developers to create hybrid applications, implying a larger mix of tools, libraries, and interoperability issues. There is more work to meet growing expectations around privacy, security, and accessibility.
There are many ways to focus on developers. Many W3C activities outside of standards development are geared toward enabling developers, including tools (validator), documentation (Web Platform Docs), training (W3DevCampus, W3Conf), participation (Community Groups, draft Webizen program).
The question I want to get at in this post, however, relates to our open standards agenda: are we building the platform that developers need? How can we find out?
That is where the Application Foundations come in. They give us a way to think about the Open Web Platform that will make it easier for the W3C community to converge on the top priorities for developers.
Platforms mature predictably in the following way: at a given time, some capabilities are core and "applications" rely on the core. Invariably, there comes a time when certain features are so pervasively used as services by other applications, the "next generation" of the platform must subsume some of those features (via libraries, platform services, daemons, etc.).
Operating systems provide a familiar example. Typically, an operating system kernel provides the key lower layer functions that a computer needs for its programs (aka applications): program execution, memory management, support for devices, etc. In early versions of many operating systems, there are also higher layer functions (such as networking, security, GUIs, etc.). Often these functions have some manifestation in the kernel, but also some manifestation in applications. Over time, given experience with the higher layer functions, people recognize that some must mature into major subsystems (aka foundations) that are above the kernel, leveraged by many applications. Modular design of these subsystems allows experts in different areas (security, communications protocols, and so on) to deliver solutions that will best serve all the other parts of the platform.
We see this pattern with the Open Web Platform as well. There was a time that video would have been viewed as an application of the Web, but in HTML5, video has unquestionably been absorbed into the core infrastructure (e.g., via the HTML <video> element). An apt metaphor is to call the programmable Open Web Platform of today the first generation operating system of the Web. In the past couple of years, important subsystems have already started to emerge, and in this post I propose a taxonomy of eight Application Foundations to focus our discussion on the next generation:
Each Foundation represents collection of services and capabilities that should be available for all applications. For example, the Security and Privacy Foundation includes capabilities such as crypto, multi-factor authentication, and resource integrity.
We expect each Foundation to evolve independently, driven by experts in that topic. We also know that there will be interconnections, such as Security implications of Device Interactions, or Accessibility considerations of streaming Media.
Below I will begin to enumerate the capabilities we have associated with each Foundation, both long-standing and new or planned work that will substantially advance the capability of the OWP.
In our internal discussions there was quick consensus on the usefulness of an Application Foundations paradigm. There was also passionate debate about taxonomy itself. Did we come up with one that will speak to developers? Did we neglect some important piece of functionality? Should this or that second-level item be a top-level category or vice versa? To help structure the broader debate to come, I'd like to provide some background for the choices proposed here.
Bearing in mind that we are looking for a best fit to structure discussion, not a perfect dissection, here are some key principles for thinking about these Foundations:
Although this framework is meant initially only as a communications vehicle —a way of describing the substantial work we have to do to enhance the OWP— we may find other uses later. Once fleshed out and road-tested, for example, the W3C Technical Architecture Group (TAG) might use this model for architectural discussions about the Open Web Platform.
Ultimately, with such a framework, it becomes easier to identify what is missing from the platform, because we will think more cohesively about its key components. And where there are similar capabilities (e.g. different functions that show up in the same Foundation), it will make it easier to identify where synergies can simplify or improve the platform.
By definition, Foundations are common subsystems useful not only for "horizontal applications", but also for a variety of industries such as digital publishing, automotive, or entertainment. In a separate exercise we plan to work with those industries to create a view of the Foundations specific to what they need from the Open Web Platform.
So let's get started. In each paragraph below, I outline why we think this area deserves to be a Foundation. I list some absolutely critical problems the community is currently addressing. This will help motivate why each Foundation was chosen, and the technology development required to give rise to the next generation Web.
The Web is an indispensable infrastructure for sharing and for commerce. As we have created the OWP, we have become increasingly sensitive to making this a secure infrastructure. See, for example, our 2013 "Montevideo" statement calling for greater Internet security.
The vulnerabilities have become increasingly prominent. They vary in range and style. There are vulnerabilities that result from criminal exploitation of security holes for financial gain. There are numerous situations where information and communications that was intended to be private has found its way into unauthorized hands.
From a pure technical point of view, there is a tremendous amount of security research and there is knowledge on how to make an infrastructure secure. Many security advances are available in devices that are connected to the Web today. Nonetheless, security exposures abound: because it is too difficult for applications to leverage the security that is available; because new security techniques are not yet in place; and because users are not encouraged to rely on strong security.
We do not expect all developers to be security experts, so we must make it easier to use the security mechanisms of operating systems. The Crypto API provides access to some of those services from within JavaScript, and is already being deployed. This trend will be extended as platforms add stronger security such as multi-factor authentication, biometrics, smartcards, all discussed at our September Workshop on Authentication, Hardware Tokens and Beyond. We also need to add a more comprehensive Identity Management system which discourages weak passwords.
To strengthen this Foundation, we are working closely with a number of organizations, including the IETF, FIDO Alliance, and Smartcard Alliance.
Developers use many widely deployed front end technologies for structure, style, layout, animations, graphics, interactivity, and typography of pages and apps. HTML5 brought native support for audio and video, canvas, and more. Dozens of CSS modules are used for advanced layout, transformations, transitions, filters, writing modes, and more. SVG is now widely supported for scalable graphics and animations, and WOFF is beautifying the Web and making it easier to read.
Still, the work is not complete. Much new work will be driven by the adoption of the Web on a broader set of devices, including mobile phones, tablets and e-book readers, televisions, and automobiles. The responsive design paradigm helps us think about how we need to enhance HTML, CSS, and other APIs to enable presentation across this wider set of devices.
One exciting direction for this Foundation is Web Components, which will make it easier for developers to carry out common tasks with reusable templates and code modules, all leveraging standards under the hood.
Another area of anticipated of work will be driven by a more complete integration of digital publishing into the Web. In the past, advanced styling and layout for magazines has remained an area where special purpose systems were required. In this Foundation, we will ensure that we have the primitives for advanced styling and layout so that all publishing can be done interoperably on all Web devices.
Our Test the Web Forward activity, though relevant across the Foundations, has been particularly influential for Core Web Design and Development, and we invite the community to contribute to that active testing effort.
Closely related to the Core Foundation is the Device Interaction Foundation, which describes the ways that devices are used to control or provide data to applications. New Web APIs are proposed weekly to give access to all of the features offered by supporting devices. For mobile phones, APIs exist or are in development for access to camera, microphone, orientation, GPS, vibration, ambient light, pointer lock, screen orientation, battery status, touch events, bluetooth, NFC, and more.
The next generation of Web attached devices will introduce new challenges. For instance, the Automotive and Web Platform Business Group is developing APIs to access information about vehicle speed, throttle position, interior lights, horn, and other car data that could help improve driving safety and convenience. We anticipate some of that work will advance to the standards track. In general, wearables, personal medical equipment devices, home energy management devices, and the Internet of Things will drive developer demand for data in applications, and for Web abstractions to simplify what will be new complexity in underlying networks. To achieve that simplicity for developers, the TAG, Device APIs Working Group, Web Apps Working Group, and Systems Applications Working Group all have a role to play in capturing good practices for API design.
The proliferation of environments —both mobile and non-mobile— in which an application may run has created new challenges for developers to satisfy user expectations. People expect their apps to be useful even when there is no network ("offline"), to do the right thing when the network returns ("sync"), to take into account location-specific information ("geofencing"), to be easy to launch on their device ("manifest"), to respond to notifications (from the local device or remote server), and so on. The Application Lifecycle Foundation deals with the range of context changes that may affect an application. For example, developers have made clear that that AppCache fails to meet important offline use cases. so we must come up with a superior solution.
The emerging approach ("Workers") for addressing many these lifecycle requirements involves spawning important tasks as asynchronous processes outside of an application. For instance, a Worker can be used to manage a cache and update it according to network availability or receive server-sent notifications, even when an application is not actively running. Enhancing these Foundations these will enable developers to create superior user experiences.
A number of communications protocols and related APIs continue to serve developers well, from HTTP to XMLHttpRequest to Web Sockets. But to meet the growing demand for real-time communications and streaming media, we must add new capabilities, the focus of this Foundation.
The promise of WebRTC is to make every single connected device with a Web browser a potential communications end point. This turns the browser into a one-stop solution for voice, video, chat, and screen sharing. A sample use case driving interest in real-time in the browser is enabling "click-to-call" solutions for improved customer service. WebRTC has the potential to bring augmented reality to the Web and create a brand new class of user experiences – an exciting direction for this Foundation.
For audio and video, developers will have a variety of tools to manipulate media streams, edit audio input, and send output to multiple screens ("second screen"). This last capability is of particular interest to the entertainment industry. For example, in the US, a majority of people have a second device nearby while watching television, allowing for new interactive experiences such as social interactions or online commerce.
Open Web Platform functionality has moved steadily to the client side, which creates a variety of new challenges related to security, application lifecycle management, but especially performance. JavaScript engines have improved dramatically in the past few years. But for high-end games, media streams, and even some simple interactions like scrolling, we still have much to do so that developers can monitor application performance and code in ways that make the best use of resources. This is the focus of our Performance and Tuning Foundation.
Today we are working on APIs for performance profiling such as navigation timing and resource hints. In various discussions and Workshops, people have asked for a number of enhancements: for understanding load times, enabling automatic collection of performance data, providing hints to the server for content adaptation, improving performance diagnostics, managing memory and garbage collection, preserving frame rates, using the network efficiently, and much more.
The responsive design paradigm mentioned in the Core Web Design and Development Foundation also plays a role in the world of performance: we can make better use of the network and processing power if we can take into account screen size and other device characteristics.
The richness of the Open Web Platform has raised new challenges for some users. It is great to be able to create an app that runs on every device, but is it easy to use or klunky? It's great to offer streaming media, but do developers have the standards to include captions to make the media accessible?
Designers have pioneered a number of approaches (responsive, mobile first), that can improve accessibility and usability, and W3C's Web Accessibility Initiative has developed some standards (such as WCAG2 and WAI-ARIA) to enable developers to build accessible applications. But we have more work to do to make it easier to design user interfaces that scale to a wide array of devices and assistive technologies. We have confidence that designers and developers will come up with creative new ways to use standards for new contexts. For example, the vibration API used by some mobile applications might offer new ways to communicate safely with drivers through the steering wheel in some automotive apps, and could also be used to create more accessible experiences for people with certain types of disabilities.
Less than one third of current Web users speak English as their native language and that proportion will continue to decrease as the Web reaches more and more communities of limited English proficiency. If the Web is to live up to the "World Wide" portion of its name, it must support the needs of world-wide users at a basic level as they engage with content in the various languages. The W3C Internationalization Activity pursues this goal in various ways, including coordination with other organizations, creation of educational materials, coordination on the work of other W3C groups, and technical work itself on various topics.
Earlier I mentioned the pattern of widely used applications migrating "closer to the core." While this is true for all the Foundations, it is especially clear in the Services Foundation, where today we are exploring the four most likely candidates for future inclusion.
The first is Web payments. Payments have been with us for decades, and e-commerce is thriving, predicted to reach $1.471 trillion this year, an increase of nearly 20% from last year. But usability issues, security issues, and lack of open standard APIs are slowing innovation around digital wallets and other ways to benefit payments on the Web. W3C is poised to launch a group to study the current gaps in Web technology for payments. The Payments group will recommend new work to fill those gaps, some of which will have an impact on other Foundations (e.g., Usability, Security and Privacy). Because a successful integration of payments into the Web requires extensive cooperation, the group will also liaise with other organizations in the payments industry that are using Web technology to foster alignment and interoperability on a global scale.
The second is annotations. People annotate the Web in many ways, commenting on photos or videos, when reading e-books, and when supporting social media posts. But there is no standard infrastructure for annotations. Comments are siloed in someone else's blog system, or controlled by the publisher of an e-book. Our vision is that annotations on the Web should be more Web-like: linkable, sharable, discoverable, and decentralized. We need a standard annotation services layer.
The third is the Social Web. Consumer facing social Web services, combined with "bring your own device (BYOD)" and remote work policies in enterprise, have driven businesses to turn increasingly to social applications as a way to achieve scalable information integration. Businesses are now looking for open standards for status updates (e.g., Activity Streams) and other social data. These same standards will give users greater control over their own data and thus create new opportunities in the Security and Privacy Foundation as well.
The fourth is the Web of Data. The Semantic Web and Linked Data Platform already provide enhanced capabilities for publishing and linking data. These services have been used to enhance search engines and to address industry use cases in health care and life sciences, government, and elsewhere. But we know that more is necessary for developers to make use of the troves of data currently available. One upcoming activity will be to collect ontologies of how linked data should be organized for different applications (notably for search).
Web technology continues to expand by leaps and bounds. The core capability is growing, the application to industry is growing, and we continually find new devices for web technology and new use cases. To be able to focus on this expansion we need modular design, and a principle in modular design is to be able to clearly and succinctly talk about categories of function. Hopefully this post begins a healthy discussion about the framework for the Open Web Platform going forward.
As part of that discussion will continue to develop a new Application Foundations Web page and invite feedback via our public Application Foundations wiki.
I acknowledge extensive discussions within the W3C Team, but especially with Phil Archer, Robin Berjon, Dominique Hazaël-Massieux, Ivan Herman, Ian Jacobs, Philippe Le Hégaret, Dave Raggett, Wendy Seltzer, and Mike Smith. At the Extensible Web Summit, I received great input from Axel Rauschmayer, Benoit Marchant, and Alan Stearns.
This is the 3-10 October 2014 edition of a "weekly digest of W3C news and trends" that I prepare for the W3C Membership and public-w3c-digest mailing list (publicly archived). This digest aggregates information about W3C and W3C technology from online media —a snapshot of how W3C and its work is perceived in online media.
[What was tweeted frequently, or caught my attention. Most recent first]
600) Dev.Opera: CSS: It
was twenty years ago today — an interview with Håkon Wium
80) Automotive:
Accelerating the Adoption of Web Technologies in the Automotive
35) HTML5 wearable: Hoodie
season is here. Bundle up and wear your HTML5 badge proudly! @html5
@w3c @html5guy
620) Hybrid apps: HTML5
Has A New Best Friend—And It's Apple, Not Google
22 articles since the last Digest; a selection follows. You may read all articles in our Press Clippings page.
Twenty years ago today, Opera's CTO Håkon Wium Lie published Cascading HTML style sheets – a proposal. If Paul McCartney were a web developer, and writing 'Sergeant Pepper's Lonely Hearts Club Band' today, he would almost certainly write:
It was twenty years ago today
That Håkon wrote a doc to say
That if the Web's gonna last a while
Then we need a way to define style.
So may I introduce to you
a way to add visual treats:
It's Sergeant Håkon's Cascading Style Sheets!
However, when we went round to Paul's house to ask him to sing
this for us, he declined and set his guard dogs,
FontTag and
Bgcolor, on us. So, instead,
to mark this occasion, Bruce sat down with Håkon to ask a few
questions about the past, present and future of CSS.
CSS was conceived twenty years ago. Are you happy about how your baby, child and teenager has turned out?
Yes, I'm very happy with CSS. CSS is a cornerstone web specification and web pages are more beautiful as a result of CSS being there. The fact that HTML is still alive and well is also a testimonial to the success of CSS. As with all youngsters, however, there is room for improvement.
You've been quoted as saying you proposed CSS "to save HTML". Please explain.
HTML would have been very different if CSS had not appeared.
Authors who came to the web from a desktop publishing background
were baffled by the lack of
<color> and
 tags. Including myself. In my first real
publication on the web, I resorted to making images with text in it
— you can see it in this
publication from 1993. If this development had continued, the
web would have become a giant fax machine where pictures of text
would be passed along. This would have been terrible for blind
users and search engines alike. CSS was proposed to prevent this
development by giving authors a way to express their designs
without adding new HTML tags.
In the first proposal, there was a percentage of
influence specifier, e.g.
h1.font.size = 24pt 100%,
described as follows:
The percentage at the end of the line indicates what degree of influence that is requested (here 100%). If this is the initial style sheet (i.e. the one under user control), this request can be fulfilled, i.e. all headline elements will be rendered using Helvetica. If the statement comes in a later style sheet, any unclaimed influence is granted.
Why was this dropped?
The mechanism you refer to was there to try combine the needs
and preferences of both authors and readers. It was inspired by an
idea from the MIT Media
Lab: TVs in the future would not have controls for brightness
and color, but for sex and violence, or left-wing and right-wing,
perhaps. The CSS proposal was to have sliding scale where the
author was fully in charge in one end of the scale, and the user
was fully in charge in the other end of the scale. In between, the
browser would try to mix requests to make everyone happy. This
works well for certain properties (like
font-size) but
is hard to do for others (like
font-family). In his
first response to the CSS proposal,
Bert criticized this idea:
The idea that two designs can be averaged to come up with an intermediate style seems utterly wrong to me. What happens when my blue-on-yellow style is combined with somebody else's yellow-on-blue? Do I get green-on-green? Or who wants to look at a page with Avant-garde titles over Helvetica paragraphs?
Some attributes mix better than others. A typical use of "weighted average" is to soften the author's attempt to be distinct, e.g. the suggested font sizes – while the user still gets the message. One doesn't have to use this feature, but while "100%" is equal to a binary "1" there is no going back from a binary syntax. In general, I think computer interfaces are much too binary.
Of course, Bert was right (he is, almost always) that the proposal created more problems than it solved, and the mixing was dropped.
Ditto the JS-style dot syntax. Why did it change?
It's interesting you call it JS-style syntax. When I first proposed CSS, JavaScript was not around so I couldn't borrow it from there. Rather, the syntax was inspired by X resources from the X11 Window System, another inspirational project coming out of MIT.
The reason for changing the CSS syntax from
font.size to
font-size was twofold.
First, the hyphen makes it look more like written English, which
improves human readability. Second, DSSSL and
used hyphenated property names. James Clark, who wrote the first
draft of DSSSL-Lite, participated in the first W3C workshop on
style sheets, and Bert and I borrowed the hyphen from DSSSL. On
the downside, the hyphen represents minus in math, which sometimes
confuses parsers.
How did Bert Bos get involved, and how did you work together?
Bert Bos reviewed my initial proposal. His background and focus was a bit different from mine, but when he wrote up his own proposal we quickly realized that two proposals could be combined into one. At that point, the web project was being kicked out of CERN and W3C was formed. I was starting up the European branch of W3C at INRIA and Bert was hired immediately. Most of CSS1 was hammered out on a whiteboard in Sophia-Antipolis in July 1995. Bert is still working for W3C in Sophia-Antipolis. Whenever I'm struggling with a difficult technical problem, I wish Bert and the whiteboard were there.
When listing people who made CSS possible, I must also mention Thomas Reardon and Chris Wilson of Microsoft. Thomas was the program manager for Internet Explorer (IE) who early caught onto the idea of adding style sheets to the web. Chris Wilson was the programmer who added CSS to IE3. IE3's implementation was far from the standard, but one must remember that it was released before CSS1 was finished. Simon Daniels (also of Microsoft) wrote some impressive demos in IE3, and together they committed a major software company to support an emerging standard.
Were there any competing proposals? Why was yours better?
There were a dozen or so proposals for style sheets languages to be used. However, not all of them were suitable due to the characteristics of the web. For example, browsers use progressive rendering to display documents, and they must handle situations where style sheets are not accessible. There's a wide range of web devices out there and you can't write a style sheet for each one. So, style sheet languages must express designs that are scalable and responsive. It's a fascinating area of study and I've written a PhD Thesis, which compares the approach taken by the various style sheet proposals.
Naturally, I'm biased in the second part of your question. But I
believe CSS has several notable features which makes it especially
suitable for web use: cascading, pseudo-classes and
pseudo-elements, forward-compatible parsing rules, support for
different media types, strong emphasis on selectors, and the
em unit.
What's the biggest mistake you (and Bert) made?
I devote a chapter in my PhD thesis to problems in CSS. There are some, even self-inflicted ones. But the biggest problem CSS1 experienced was not in its design (which is pretty good, if you ask me), but rather in the initial implementations. Jeffrey Zeldman described the situation:
If Netscape 3 ignored CSS rules applied to the
element and added random amounts of whitespace to every structural element on your page, and if IE4 got
right but bungled padding, what kind of CSS was safe to write? Some developers chose not to write CSS at all. Others wrote one style sheet to compensate for IE4's flaws and a different style sheet to compensate for the blunders of Netscape 4.
Microsoft and Netscape both deserve some blame, but we — me, Bert, W3C — could have avoided many problems by producing a test suite along with the CSS1 specification. The first real CSS test appeared in October 1998 when Todd Fahrner published his Acid test. The test was creative, visual, and developers could immediately see whether they passed the test or not. In the beginning, no browsers passed. But then, with a strong push from the CSS community, things started to improve. The WaSP played a key role in assuring support for standards. The Opera browser also played a role by showing it was actually possible to implement CSS correctly. When I realized how solid Opera's CSS implementation was — much better than Microsoft's or Netscape's — I joined Opera.
One of Opera's claims to fame before I joined was that the browser would fit on a floppy disk (which is 1.44 MB). "Fits on a floppy" was a great slogan in those days. When CSS was added, a few more bytes were needed and Opera would no longer fit. "Almost fits on a floppy" doesn't quite have the same ring to it.
The original Acid test inspired Acid2 and Acid3, which use the same formula: a visual and demanding web page which tests a wide range of features. The development of Acid2 was triggered by an open letter from Bill Gates, where he praised interoperability. Making IE7 follow the CSS standards seemed like a natural follow-up item, and Microsoft was challenged by Acid2. In fairness, other browsers also had issues, and Acid2 exposed bugs in all of them. Microsoft ignored Acid2 in IE7, but — magic sometimes happens — IE8 supported it perfectly. As do all current browsers.
Why did you decide on the box model whereby margin,
padding, border are added to declared width rather than the IE5
box-sizing: border-box model?
There are good use cases for both models, I believe. If you want
want an image to stretch out to fill the whole content box, the
original CSS box model is the one to use. However, if it's
important that padding and borders do not extend outside a certain
area, the IE5 model is better. Personally I think there are more
use cases for the CSS box model, but some people that I respect
highly think otherwise. The conflict has been gracefully resolved
by the addition of the
box-sizing property which all
browsers now support.
I've always disliked absolute positioning. Am I wrong? How did it come about in the spec?
Your question takes me back to some heated debates in 1996. The
short story is that Microsoft proposed absolute positioning in a
draft called
CSS Regions: Absolute Positioning and Z-Ordering (discussions
took place on W3C member-only lists, I'm afraid; the closest public
document is WD-positioning).
Several members of the newly formed CSS Working group had
reservations, and Bert and I wrote up
a simplified counter-proposal. Our proposal got rid of the
position property (
display was used
instead) and only described relative positioning (which would give
us time to think through absolute positioning). Microsoft, however,
had already implemented their proposal and were reluctant to remove
functionality. In the end, the only material changes were to add
right and
bottom properties (to
left and
top), and to add
position: fixed. This became
part of CSS2.
Like you, I have never become comfortable with absolute positioning. That being said, absolute positioning has found its place on the web and I use it from time to time to achieve things that would otherwise be hard, if not impossible, to encode.
I've heard people say that you shouldn't use floats for layout, as they "weren't intended" for that — they were just to wrap text around images. Does the intention matter, if they work?
Having text wrap around images is one of the basic layout techniques. For sure, floats should be used for layout. One area I'd like for CSS to progress into is paginated onscreen presentations. When you paginate content, floats become even more useful because you can float elements to the top and bottom of the screen.
If you could wave a magic wand, which bit of current CSS would you banish from the world, and what would you magically add and implement everywhere?
I'd banish browser-version-specific code like:
lt IE 7 ]>. While technically not expressed in CSS, these
kinds of "comments" should not be necessary and they lower the
standards of the web.
The second part of your question is even more interesting: what
parts of CSS should be magically implemented everywhere? In 2006, I
would have said
web fonts. In 2007, I would have said the
<video> element (straying into HTML-land for
a while). Both of these are now implemented in all browsers.
In 2011, seeing that many apps used pages (and not scrollbars)
to create compelling presentations, I started advocating for
web pages to
become real pages. The idea is that the style sheet would
trigger paged mode so that content is split into pages. Users would
navigate from one page to the next with gestures, or perhaps with
PageUp and
PageDown. I want it to be
possible, even easy, to create ebook-readers in browsers. For this
to happen, a bit of magic would be helpful. Could you sprinkle some
fairy dust on the pillows of all browser vendors, please?
But CSS is not just for browsers. Bert and I wrote a book on CSS and in 2005, for the third edition, we wanted to use CSS itself for formatting. The browsers were not up to the job, but then Prince came along. Michael Day and his colleagues in Melbourne made a terrific product which was able to create a beautiful PDF document from HTML and CSS which we could send to the printer. In order to them to fix my favorite bugs, I joined the board of directors. Prince has since been used to format hundreds of books. We will still have some paper books in the future, I believe. And they will be made from HTML and CSS.
Why do we still not have a method of laying out pages in CSS that doesn't require a Doctorate in Rocket Surgery? (I'm looking at you, Flexbox…)
Layout is complex, and layout on the web is even more complex due to pages being displayed on so many different devices. CSS has several mechanisms for laying out content, including absolutely positioned elements, floats, multi-column layout, and CSS tables. The interaction between them can be complex, but I don't think any doctorate is needed. I must admit to not having used Flexbox much, though.
What's your opinion on pre-processors like SASS and LESS? Does CSS have anything to learn from them?
Yes, pre-processors make a lot of sense. We should probably take
the five or so most popular features from pre-processors and add
them to CSS itself. My own favorites would be nested selectors, and
single-line comments (starting with
//). When CSS
turns 50 I'll tell you why they were not part of CSS from the
You're one of the members of the WHATWG. How did that come about?
WHATWG was formed when it became clear that W3C would abandon work on HTML and instead focus efforts on compound documents based on XHTML, XForms, SMIL and SVG. For browser makers, HTML was much too important to abandon. Therefore, Ian Hickson, who, at the time, worked in my group at Opera, set up WHATWG to continue working on the web as we know it. Also, we were concerned about Microsoft's XAML, which had a thin layer of XML on top of a proprietary application language. The focus of WHATWG is therefore on applications, rather than documents. Ian continues to do an amazing job as the editor of the HTML standard.
You're the father of CSS, yet you've recently published some specs under the WHATWG domain rather than the CSS WG in the W3C. Why?
Indeed, CSS Figures and CSS Books are work items of WHATWG. There are some important benefits to publishing the specification in WHATWG. The "living standard" model allows quick updates with little overhead; in the past it was difficult to publish W3C Working Drafts in this area. WHATWG's goal of keeping the specifications a little ahead of the implementations but not so far ahead that the implementations give up is one that I strongly believe in.
Finally, is CSS still up to the job? Or should we try to move to another model — for example, Grid Style Sheets?
Ethan Munson and Philip M Marden wrote in 1999 that "style sheet languages are terribly under-researched". This remains true today, and efforts to research and improve style sheet languages must be encouraged.
GSS is an interesting example which adds the "Cassowary" constraint solver to the style sheet mechanism. In my initial CSS implementation in 1995 I used the "SkyBlue" constraint solver to resolve conflicting style sheet statements. (By the way, "SkyBlue" and "Cassowary" were both developed at the University of Washington.) Having a constraint solver allows you to express relationships between arbitrary elements and have conflicts resolved automagically. However, things can get complex when elements disappear and new ones arrive, like they do through DOM operations. Circular dependencies must also be handled gracefully. Therefore, the idea of allowing CSS to express layout constraints between any elements were dropped at an early stage.
Returning to your question: is CSS still up for the job? I think so. I don't see anything on the horizon that makes me think otherwise. New ideas will come along, but they will extend CSS rather than replace it. I believe that the CSS code we write today will be readable by computers 500 years from now.
Thank you. Happy CSS Birthday!
The CSS Working Group has published an updated Working Draft of CSS Regions Level 1. CSS Regions gives the ability to say, "Display this content (a named flow) over there (a region chain)."
The changes from the last public working draft are only in the introduction. You may have looked into CSS Regions in the past and thought to yourself, "Magazine-style layout isn't relevant to me." If you have, please take a look at the new intro which now shows much more basic examples and motivations for the feature.
Please send feedback to the (archived)
public mailing list
firstname.lastname@example.com with the spec code
[css-regions]) and your comment topic in the subject
(Alternatively, you can email one of the editors and ask them to forward your comment.)
There has been discussion in the Web standards community about which is the better way to advance technical specifications: by a formal consensus process or by having all decisions made by informed editors as they informally gather a consensus. After all, the W3C has long considered consensus a core value of W3C. On the other hand, the WHATWG describes a process whereby the relevant editor makes the decisions by trying to see where the consensus is, and is explicit about eschewing formal consensus. Which approach is better?
In my view, there are advantages to either approach. Clearly when there is an excellent spec writer who works with colleagues there is tremendous efficiency to having decisions made by informed editors. People make excellent progress with this approach both in the WHATWG and in many W3C Groups, including Community Groups (which typically have a high degree of flexibility in how they approach spec writing). In W3C Working Groups it is often the case that an informed editor is able to rapidly make progress in writing a spec and produces Working Drafts with the results. A W3C Working Draft does not necessarily represent a consensus of the Working Group, as it is not a finished product of the group.
While rapid progress can be made by informed editors, W3C will not give its imprimatur that a specification is a "Standard", or a W3C Recommendation, however, unless it goes through the formal consensus process.
Billions of people and millions of developers rely on Web standards. Since the Web was invented by W3C Director Tim Berners-Lee 25 years ago, it has become a core infrastructure for personal communications, commerce, education, and entertainment. While implementers of standards can rapidly interact with informed editors, it is important that the entire ecosystem has the confidence of due process and is assured that they have their say. This ecosystem includes those who implement standards in browsers, web site developers, app developers, users, people with disabilities, corporate IT, procurement officers, telecommunication firms, ISPs, publishers, news outlets, marketing professionals, on-line e-commerce sites, researchers, educators, textbook authors, and de jure standards organizations such as the International Organization for Standardization (ISO). Significantly, the community is global.
To appreciate why this is important and necessary, it is worthwhile to review some of the key principles of OpenStand and explain their motivation.
As described in OpenStand, the consensus process has the right properties for developing standards as critical and pervasive as web standards. However, there are tradeoffs, prominent among them that introducing review and accountability to those review comments typically has an impact on speed and agility. We have much to learn from other processes such as "decisions by informed editors". We are currently looking at a prime example of that, HTML4 was standardized in 1999, and it is taking us 15 years to get to HTML5 – due to be standardized later this year. Three years ago we began revamping our processes in W3C to achieve much of the agility that the industry needs, without sacrificing OpenStand principles. Here are some of the key recent process innovations that W3C has taken to get the best of both worlds.
There are advantages to having decisions made by informed editors. But W3C must keep its commitment to the OpenStand consensus principles. For good reasons as described above. At the same time, we must improve our processes to foster agility and learning from other approaches.
This is the 26 September – 3 October 2014 edition of a "weekly digest of W3C news and trends" that I prepare for the W3C Membership and public-w3c-digest mailing list (publicly archived). This digest aggregates information about W3C and W3C technology from online media —a snapshot of how W3C and its work is perceived in online media.
[What was tweeted frequently, or caught my attention. Most recent first]
1305) Milestone: 1-Oct – W3C
20th anniversary [tweet,
Improving typography on the Web and in eBooks
Also) Adobe:
Drop Caps Are Beautiful, Sylvain Galineau [+ Demos]
20) a11y: Carousel Concepts
• Carousels • WAI Web Accessibility Tutorials
9 articles since the last Digest; a selection follows. You may read all articles in our Press Clippings page.
setProperty() according to last week's proposal
following Rossen's approval
animation-fill-mode applies
whenever it's updated
About a fortnight ago, the CSS WG published an updated Working
Draft of the CSS
Display Level 3. This module describes how the CSS formatting
box tree is generated from the document element tree and defines
properties (like the
display property) that control
the types of boxes thus generated.
Significant changes since CSS2.1 include:
display into
display-outside to independently control the
layout mode inside the box and its role in the parent formatting
context, respectively.
display: run-in, but with more
reasonable behavior than was in CSS2.1 before it was dropped.
display: contents value that eliminates
the element's own box and brings its children up to act as children
of its parent box.
Significant changes since the previous draft are listed in the Changes section.
We have a couple of key issues open that we would particularly like feedback on:
display: contents and counter
numbering: specifically, comments from implementers about the
implementability of various options, and comments from authors
about how they'd expect the numbering to behave.
speak property) from CSS Speech. (Likely we'll
speak: auto depend on the value of
box-suppress, but we're open to other
Our plan going forward is to resolve all the open issues
(obviously), defer the longhands of
display to another
and hopefully transition to CR in the next six months.
As always, please send feedback to the (archived)
public mailing list
email@example.com with the spec code
[css-display]) and your comment topic in the subject
line. Alternatively, you can email the editors and ask them to
forward your comment, or post a comment here.
The CSS Working Group has published another Last Call of CSS Flexible Box Layout Level 1 in response to feedback on the recent changes. Flexbox is a new layout model for CSS: the contents of a flex container can be laid out in any direction, can be reordered, can be aligned and justified within their container, and can "flex" their sizes and positions to respond to the available space. This is an update to fix various problems, particularly in the layout algorithm, found through implementation review and experience during the Candidate Recommendation phase. As before, the CSSWG is not revoking the call for implementations: we're just issuing an LCWD to process the changes.
To help with review and with correctly updating implementations, exact diffs since the original Candidate Recommendation, and their justifications, are available in the Changes section. A Disposition of Comments is also available. The Last Call comment period ends 25 October 2014: please either send comments by then, or request an extension; we plan to process them during TPAC.
As always, please send feedback to the (archived)
public mailing list
email@example.com with the spec code
[css-flexbox]) and your comment topic in the subject
line. (Alternatively, you can email one of the editors and ask them
to forward your comment.)
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.


text:
Local Veterinarians in Your Area
628 Haddonfield Rd, Cherry Hill, NJ 08002
If you live in Cherry Hill or the surrounding area in NJ, then you have picked the perfect site to find a veterinarian. Our veterinarians are licensed in treating all types of pets and animals. Your pet's health and well being is very important to us and we will take every step to give your pet the
1785 Springdale Rd, Cherry Hill, NJ 08003
Established for over two decades, The Animal and Bird Health Care Center and Hospital has been providing high quality medicine, surgery, and dentistry for dogs, cats, birds, small mammals and reptiles. Conveniently located near the NJ Turnpike and I-295, the Animal & Bird Health Care Center
726 Alexander Rd, Princeton, NJ 08540
Welcome to Princeton Animal Hospital & Carnegie Cat Clinic, a full-service, technologically advanced dog and cat veterinary facility located in Princeton, New Jersey. Owners and veterinarians Drs. James and Terry Miele, as well as their staff of veterinarians, veterinary technicians and assistants,
315 West Route 70, Marlton, NJ 08053
Banfield is a convenient, affordable and wise choice for all of your Pet's healthcare needs. We take an innovative and caring approach to healthcare that enables us to consistently provide Pets with the same level of care we want for ourselves. In keeping with our commitment to quality, eachview deal
827 Bethlehem Pike, Flourtown, PA 19031
Welcome to Montgomery Animal Hospital. We have been in operation for over 50 years. We are a full-service veterinary hospital and have been certified by the American Animal Hospital Association since 1972. We pride ourselves on being a friendly practice that provides superior medical care,
380 North Shady Retreat Rd., Doylestown, PA 18901
The doctors and healthcare team at Doylestown Veterinary Hospital strive to offer the old-fashioned tradition of compassionate care along with modern techniques and medical innovations. At our hospital our goal is to get to know your pets as members of your family, and develop a lasting
617 N Bethlehem Pike, Lower Gwynedd, PA 19002
Springhouse Animal Hospital welcomes you and your pets! Our highly-trained staff is knowledgeable in the latest techniques to ensure that your beloved companion gets the best care possible. Spring House Animal Hospital is committed to providing only the finest traditional and holistic veterinary
800 N Easton Rd, Doylestown, PA 18902
Founded by Dr. Dale Mantell in 1983 with the purpose of establishing a local, comprehensive veterinary clinic, the Doylestown Animal Medical Clinic has grown for nearly three decades into a facility praised for its care and professionalism throughout Bucks County and beyond. With a roster of
40 White Horse Pike, W. Collingswood, NJ 08107
Collingswood Veterinary Hospital has been providing veterinary services to pets for over 75 years. Our goal is to ensure the complete satisfaction of every customer, while offering knowledgeable, friendly and exceptional quality service. The doctors and staff of Collingswood Veterinary Hospital
920 Town Center, New Britain, PA 18901
Welcome to Circle of Life Veterinary Center! Our Mission Statement: To nurture the human / pet bond by working in partnership with the owner to ensure the highest quality of life through their entire journey together. It is our goal to provide exceptional medical treatment and preventativeview deal

subset: commoncrawl


text:
While the Boy Scouts of America
maintains a strong financial position, in order to continue to deliver the
nation's foremost youth program, it is occasionally necessary to increase
membership fees so that we can offset rising administrative costs.
For this
reason, the Boy Scouts of
America is increasing its membership fee from $15 to $24 per year for all
registered Scouts and adults effective January 1, 2014. Read the BSA letter and FAQs to help you better understand the increase that takes effect with the 2014 Recharter of units.
Remember Me
Forgot your password?
Haven't registered yet?
11/14/2014Second Chance Popcorn Sale!
11/12/20142015 Friends of Scouting Kickoff - Lifetime Achievement Award - Elgin Deering Award
11/14/2014 » 11/23/2014Leave No Trace Trainer Course - BSA Outdoor Ethics
11/22/2014 » 11/23/2014NCAC Cub/Webelos STEM NOVA Award _ Geology
12/1/2014Camp William B. Snyder Christmas Tree Sale
12/4/2014Council Wide Key 3 - FOS Celebration Kick-Off - Lifetime Award - Deering Award
Marriott Scout Service Center9190 Rockville Pike Bethesda, MD, 20814 P:301-530-9360 | F:301-564-9513www.BeAScout.org
Home | Quick Links | Webmaster
Site best viewed using Firefox, Chrome, Opera, Safari, or Internet Explorer 9
© 2013 NCAC, BSA.All Rights Reserved.


text:
- Shopping Bag ( 0 items )
Posted January 3, 2013
Ilove it s¿ much it was so in thused inthis book i read it twenty for hours a day.
1 out of 1 people found this review helpful.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.


text:
The Beckhams celebrate dad's final home soccer match in Paris. Plus: Tom Brady & family, Justin & Jessica, William & Harry, Jessica Simpson and more
Credit: Photopress/Splash News Online
Published: Monday May 20, 2013 | 07:00 PM EDT
More from PEOPLE
See More News
14 of 25
Is she or isn't she? As pregnancy rumors intensify, Beyoncé keeps her focus on her fans during a colorful performance in Milan, Italy, on Saturday.
Copyright © 2014 Time Inc. All rights reserved. Reproduction in whole or in part without permission is prohibited.


text:
Xbox 360
This page contains Cheats for Castle Of Illusion organized by sections for Xbox 360. Castle Of Illusion is a Action Platformer 2D game, made by Sega, released on Sep 4, 2013 and published by Sega. If you can't find a hint or secret in our list, then please check this page periodically for the latest updates.
- Developer:
Castle Of Illusion Xbox 360 CheatsSega
- Publisher: Sega
- Genre: Action Platformer 2D
- Release Date: Sep 4, 2013
- ESRB: Everyone
Complete one of the following achievements to collect their Xbox Live Gamerscore points:...From: mrmyk75
Submit Cheats
Video Walkthroughs
Stuck on this game? Set a specific, clearly defined question and let others answer your question or view answers to previously asked questions. If you think you are an Castle Of Illusion expert then please try to help others with their questions.
Ask a Question
Videos You May Like...
Castle Of Illusion - E3 2013 Trailer
- Jun 17, 2013, Views: 80
View All Videos
Castle Of Illusion - Announcement Trailer
- Aug 3, 2014, Views: 37
Game Related Options
Latest Xbox 360 Videos
- Just Dance 2015 - Gameplay Video, (Xbox360)
- Chivalry: Medieval Warfare - First Look Trailer, (Xbox360)
- FIFA 15 - Tutorial Celebrations Trailer, (Xbox360)
- NHL 15 - Gameplay Review Trailer, (Xbox360)
- Costume Quest 2 - Gameplay Video, (Xbox360)
- Slender: The Arrival - Announcement Trailer, (Xbox360)
- CastleMiner Z - Gameplay Review Trailer, (Xbox360)
- WWE '12 - Trailer, (Xbox360)
New Released Games
- Sakura Flamingo Archives, (Xbox360)
- Tales From The Borderlands, (Xbox360)
- Ask My Avatar, (Xbox360)
- Cromo Dynamix, (Xbox360)
- Samurai Showdown, (Xbox360)
- Uncraft'Em All, (Xbox360)
- Frankystein, (Xbox360)
- Dead War, (Xbox360)
- Monster Hunter Frontier G6, (Xbox360)
- Adventure Time: Secret Of The Nameless Kingdom, (Xbox360)
Popular Videos
- Kim Kardashian: Hollywood - Gameplay, (iPhone-iPod)
- Episode: Choose Your Story - Gameplay, (iPhone-iPod)
- How To Train Your Dragon 2 - Ready To Fly Trailer, (Wii)
- The Settlers - Kingdoms Of Anteria - Announcement Trailer, (PC)
- Entwined - Quick Look Trailer, (PS3)
- Blue Estate - Official Launch Trailer, (PS4)
- Goat Commando 3D Simulator - Gameplay, (iPhone-iPod)
- Munin - Official Launch Trailer, (iPad)


text:
Leading Provider of Enterprise Class Hosting Solutions, Specializing
in Cloud Hosting, Recovery & Availability. Be Always On!
horny women Chatroulette sex Uk dating bbw chat Sex adult sex ladies Sexy wife sex dates Connecting singles Girls having sex online dating Social network Relative dating FREE ONLINE DATING SITE single parent dating CHAT SEX SEXY MASSAGE Best online dating site Free online dating Xxx chat AdULT FORum AmATEUR Match SeX ADS SeX HOT Girl Married sluts Best online dating Live chat online BbW DATINg Sexy teens Erotic chat SiNGLE PArents Naughty girl BliND DAte Adult friend finder erotic chat


text:
Format Maps
Results 1 - 5 of 5
Refined by:Original Format: Maps Remove Language: English Remove Location: Maryland Remove Location: Pennsylvania Remove Subject: Delaware Remove
A plan of the west line or parallel of latitude, which is the boundary between the provinces of Maryland and Pensylvania : a plan of the boundary lines between the province of ...
Shows the Mason and Dixon line. Relief shown pictorially. First part of title appears at left margin, second part at right margin. Originally issued on 2 sheets. Available also through the Library of Congress Web site as a raster image. Includes ill. in cartouches. LC copy sectioned to 8 parts before mounting. 1 map : mounted on cloth backing ; 65 x 185 cm.
- Contributor: Mason, Charles
- Original Format: Maps
- Date: 1768
Johnson's Pennsylvania, Virginia, Delaware, and Maryland
- Contributor: Johnson & Browning
- Original Format: Maps
- Date: 1862
[Maps of the Maryland-Pennsylvania boundary used as trial exhibits in the 1735 court suit brought by the Penns against Lord Baltimore to determine the official interprovincial boundary line].
The maps also cover the Lower Counties (now the State of Delaware) which at the time were part of Pennsylvania. The "Virginia" map shows lines of latitude (identified) and longitude (unidentified). Common title devised by cataloger. Annotated in ink handwriting on recto by Ferdinand J. Paris (attorney for the Penn Family). The "Virginia" map is oriented with north to the right. Hand col. (light ...
- Contributor: Senex, John
- Original Format: Maps
- Date: 1732
Map of the seat of war /
Covers Virginia and Maryland and portions of Delaware, Pennsylvania, New Jersey and North Carolina. Shows some fortifications. Relief shown by hachures. Sewn on to and mounted on cloth backing. DLC "Entered by Evans & Cogswell according of the act of Congress of the Confederate States in the Clerks Office of the Distr. Court of the District of South Carolina." Confederate imprint. Includes inset. Available ...
- Contributor: Evans & Cogswell
- Original Format: Maps
- Date: 1861
Johnson's Pennsylvania, Virginia, Delaware, and Maryland /
- Contributor: Johnson & Browning
- Original Format: Maps
- Date: 1862


text:
Ballet Mistresses
Sarah Hillmer
Sarah Hillmer, an Atlanta native, began her professional career with Atlanta Ballet, where she performed both classical and contemporary works. She danced principal roles in classics such as Giselle, Nutcracker, Sleeping Beauty, and Swan Lake and originated roles in a variety of contemporary works. Sarah's desire to further explore contemporary movement led her to become a founding member of gloATL, where she performed the original works of Lauri Stallings in both Atlanta and New York. Sarah's love of coaching brought her back to Atlanta Ballet, where she has had the privilege of assisting and collaborating with choreographers and extraordinary dancers. She has worked as a ballet mistress to choreographers including Twyla Tharp and the Ballet's current resident choreographer, Helen Pickett. She has assisted in the restaging of works for Atlanta Ballet by choreographers such as Ohad Naharin and Wayne McGregor. Sarah has also restaged choreographers' works in New York, San Francisco, and Canada. Sarah is committed to Atlanta Ballet having an impact in the Atlanta community. This has led her to serve as rehearsal director for Staibdance and to guest teach at various institutions, including Emory University and Spelman College. Sarah is thrilled to be part of the team at Atlanta Ballet, and the possibilities therein.
Rosemary Miles
Rosemary Miles is in her 18th season with Atlanta Ballet. One of eight children of an English brigadier general, Rosemary Miles trained at Elmhurst and the Royal Ballet School in England, during which time she successfully passed all Royal Academy and Cecchetti examinations. Throughout her professional career, Rosemary danced with the Royal Ballet, the National Ballet of Canada and the London Festival Ballet. In America she performed with the educational division of the New York City Ballet and as a soloist with the National Ballet of Washington, Chicago Ballet, and Houston Ballet. Upon retiring as a dancer, Rosemary has enjoyed being a principal teacher at the Houston Ballet Academy; a guest teacher throughout the United States, England, and the Far East; artistic director of the Lexington Ballet; and a member of John McFall's artistic team for 17 years. Rosemary is the proud aunt of 22 nieces and nephews, 28 grand-nieces and nephews. Rosemary thanks the dancers of Atlanta Ballet for being such an inspiration.
Dale Shields
A native of Winston-Salem, NC, Ms. Shields graduated from North Carolina School of the Arts and Butler University before starting her career as a professional dancer. After joining and rising to principal dancer with Indianapolis Ballet Theatre, she appeared in the leading roles of many productions, including Giselle, The Sleeping Beauty, Swan Lake, The Nutcracker, Romeo & Juliet, Gaité Parisienne, A Midsummer Night's Dream, Coppélia, Night Shadow and The Moor's Pavane. Ms. Shields' artistic collaboration with IBT's artistic directors George Verdak and Dace Dindonis produced a great number of original works as well as staging and performing the Russian premiere of the ballet Le Bal in St. Petersburg, Russia. In her position as Principal Ballet Mistress for Ballet Internationale, she assisted with the original choreography of several full length ballets by Artistic Director Eldar Aliev and worked alongside Irina Kolpakova in staging many well-known Russian classics. Dale has taught on the faculty of the Academy of Ballet International and Butler University's Jorden Academy. She enjoys her time guest teaching around the country and in the Atlanta Ballet Centre for Dance Education's Summer Intensives. It has been inspiring for her to work with John McFall and the artists of Atlanta Ballet in creating new and more exciting productions every season.


text:
09-09-1996 Comments (0)
Humulin 70-30Humulin NHumulin RInsulinLillyNovo Nordisk
A US District Court in New York has granted a preliminary injunction against Eli Lilly in favor of Novo…
In order to access this content you need to be logged into the site and have an active subscription or trial subscription. Please login, take a free trial or subscribe in order to continue reading.
A trial subscription will give you access to the latest news on The Pharma Letter for 7 days, in order to evaluate the paid service.


text:
Tag Archives: mysql
Clomid For Sale
Clomid For Sale, I recently wrote a mass geolocation script in PHP since Google seems to be taking down all the websites that offer this vital service. Right now it:
- Checks a table for records without lat/long coordinates
- Sends those records' addresses to Google's geolocation API
- Updates your records with the lat/long coordinates
It checks for the "#" sign and handles it since Google has problems with translating "2020 Anywhere Place #200" as a real address, buy Clomid online no prescription, Taking Clomid, but there are probably other errors I haven't adequately checked for.
At the moment it updates records that are missing lat/long coordinates and writes zeroes into those fields if it can't geolocate the address correctly, where can i cheapest Clomid online. Clomid australia, uk, us, usa, As a result, if you run the script again, Clomid maximum dosage, Clomid coupon, it will assume those records were updated correctly and will pass over them, since they are not null, Clomid recreational. Buy no prescription Clomid online, This is a known issue and is one (of many) areas of improvement for the script.
I didn't want to spend a ton of hours on the script to make it a full-fledged awesome service, Clomid use, Clomid without prescription, since Google doesn't seem to like that. It's just a basic script that handles common problems and works well enough, Clomid treatment. Effects of Clomid, You can get it over at my GitHub repo page for GeoCode. Enjoy, generic Clomid. Where can i order Clomid without prescription. Doses Clomid work. Buy generic Clomid. Discount Clomid. Fast shipping Clomid. What is Clomid. Clomid interactions. Cheap Clomid. Online buying Clomid. Purchase Clomid for sale. Is Clomid addictive. Clomid from canada. Clomid without a prescription. Clomid dosage. Online Clomid without a prescription. Australia, uk, us, usa. Clomid pictures. Buy Clomid online cod. Buy Clomid from canada. Clomid natural. Order Clomid from mexican pharmacy. Kjøpe Clomid på nett, köpa Clomid online.
Similar posts: Pristiq For Sale. Ketoconazole Cream For Sale. Lotrisone For Sale. Prozac over the counter. Triamterene reviews. Phenergan schedule.
Trackbacks from: Clomid For Sale. Clomid For Sale. Clomid For Sale. Clomid use. Clomid treatment. Clomid online cod.
Buy Betnovate Without Prescription
Buy Betnovate Without Prescription, I've launched yet another half-complete web application relating to baseball sabermetrics. ML Splits is a database of minor league baseball players (batters only for now) that shows their "splits" (performance against LHP and RHP) as well as park effects and major league equivalencies, buying Betnovate online over the counter. Betnovate trusted pharmacy reviews, The data is taken from Jeff Sackmann's old minorleaguesplits.com site where he made the CSVs available for import as open source.
[caption id="attachment_381" align="aligncenter" width="300" caption="ML Splits"][/caption]
I leaned on jQuery for front-end display purposes, Betnovate dosage, Fast shipping Betnovate, as I'm getting more and more comfortable with using it for front-facing web applications. Mostly just dynamic div tagging and toggle() to keep the screen clear of distractions and make it easy to see what stats are really important, purchase Betnovate. Betnovate from mexico, Wrote the entire thing in PHP 5.3.x, MySQL 5, Betnovate cost, Betnovate online cod, CodeIgniter 2.0, and jQuery.
EDIT: Pitchers are up as of April 4th., Betnovate without a prescription. Betnovate samples. Buy no prescription Betnovate online. Betnovate australia, uk, us, usa. Betnovate long term. Betnovate without prescription. Where to buy Betnovate. Order Betnovate from United States pharmacy. Buy Betnovate without a prescription. Betnovate photos. Order Betnovate from mexican pharmacy. Betnovate canada, mexico, india. Where can i buy Betnovate online. Betnovate coupon. Buy cheap Betnovate no rx. Comprar en línea Betnovate, comprar Betnovate baratos. Get Betnovate. Betnovate used for. Doses Betnovate work. Purchase Betnovate online no prescription. Buy generic Betnovate. Purchase Betnovate online. Is Betnovate safe. Order Betnovate online overnight delivery no prescription. Betnovate for sale. No prescription Betnovate online. Order Betnovate no prescription.
Similar posts: Erythromycin For Sale. Buy Spiriva Without Prescription. Buy Allopurinol Without Prescription. Discount Erythromycin. Fast shipping Stromectol. Ketoconazole Cream use.
Trackbacks from: Buy Betnovate Without Prescription. Buy Betnovate Without Prescription. Buy Betnovate Without Prescription. Betnovate dose. Where can i find Betnovate online. Betnovate pics.
Phenergan For Sale
I've started to use Springloops RC2 Phenergan For Sale, for my version control efforts, which is really awesome. They support SVN and git (no Mercurial yet), Phenergan reviews, Phenergan recreational, have a great interface with easy deployments to multiple servers so you can split them up into production/staging/development, a solid ticketing system, taking Phenergan, Phenergan price, coupon, and a good code browser. Also, Phenergan results, Phenergan over the counter, it's completely free.
HeidiSQL has been my Windows MySQL GUI of choice ever since I switched to it from Toad, Phenergan price. Buy Phenergan no prescription, It's generally very good, it's FOSS, Phenergan pictures, Kjøpe Phenergan på nett, köpa Phenergan online, and it handles most operations fairly well - except for CSV importing. Site5 is my current webhost, and I'm very happy with them 99.9% of the time, but they caused me a bit of pain recently, Phenergan For Sale. I have a lot of CSVs to import that are about 10-15 MB in size each, Phenergan interactions, Rx free Phenergan, and I tried importing them through the very handy phpmyadmin tool. However, Phenergan wiki, About Phenergan, phpmyadmin has some memory leaks and issues with importing larger CSVs, so it ended up crashing due to memory problems on the larger files (even though it theoretically can handle up to 105MB CSVs), Phenergan overnight. Low dose Phenergan, I sent Site5 a ticket to have them import the CSVs manually (they said they would), but they responded with "there's no table structure in your DB so we can't do it." Well, order Phenergan online c.o.d, Phenergan brand name, uh, that's what phpmyadmin does and why I wanted to use it over the 7 tables I need to make with 20 or so CSV files, Phenergan schedule. Discount Phenergan, They refused again without providing me an alternative, so I had do it myself, ordering Phenergan online. Phenergan For Sale, I fired up HeidiSQL, manually created the tables, and imported the CSV. Phenergan duration, And... it didn't work, Phenergan pharmacy. Phenergan from canadian pharmacy, I ignored the first row (column headers), but it still responded with "invalid data." The fields were correctly cast for the rest of the data, Phenergan treatment, Phenergan class, so I didn't know what was up. A bit of Googling tells me that even if you ignore the first row, buy Phenergan from canada, Purchase Phenergan for sale, HeidiSQL still checks it against the data types in your table. This is idiotic and annoying for any number of reasons, online buy Phenergan without a prescription, Online buying Phenergan hcl, all of which I leave up to you to figure out.
At any rate, Phenergan street price, Buy Phenergan online cod, deleting the first row and ignoring 0 rows ended up working just fine. Now to do this repetitive task over and over again.., where can i order Phenergan without prescription. Where can i cheapest Phenergan online. Phenergan use.
Similar posts: Amikacin For Sale. Buy Amoxicillin Without Prescription. Buy Retin-A Without Prescription. Order Zithromax from United States pharmacy. Flagyl street price. My Cephalexin experience.
Trackbacks from: Phenergan For Sale. Phenergan For Sale. Phenergan For Sale. Buy Phenergan without prescription. Japan, craiglist, ebay, overseas, paypal. Order Phenergan online c.o.d.
Lasix For Sale
Lasix For Sale, If you're trying to build a PITCHf/x database like I am, you are probably heavily leaning on Mike Fast's work. Where can i buy cheapest Lasix online, It's a great primer, however, about Lasix, Lasix wiki, that's exactly how it should be viewed: A primer. There are numerous things that have changed since he initially wrote the page, where can i buy Lasix online, Online buying Lasix, and it's not a simple copy/paste job to download all the data from MLBAM. Among the issues are:
- Inadequate handling of timeouts from gd.mlb.com and gd2.mlb.com
- Hardcoding the IP is not a valid suggestion and causes lots of problems (suggested to get around DNS resolution issues)
- Parser script does not know how to figure out which games have been used without manually querying each at bat (expensive and unnecessary)
- Database structure is not future-proof
I could write for hours on the first three (plus other bugs), taking Lasix, Where can i order Lasix without prescription, but I didn't document them well enough and it's simply not that interesting to me to write about script bugs that people should learn how to fix for themselves. If used verbatim, get Lasix, Lasix street price, Mike's database structure will fail around July 2010 when inputting new pitches and at-bats into the database. You'll get errors like the following:
[caption id="attachment_257" align="aligncenter" width="640" caption="Yes, this is my Windows box."][/caption]
I've inserted a bunch of print statements to help me debug the code (ah, printf-style debugging) and saw that it was reporting duplicate or unknown key entries, Lasix For Sale. Recalling the little I know about MySQL and the numbers involved (513425 and later 1900131), Lasix overnight, Lasix forum, I was pretty sure that this is typical behavior when a memory space is overloaded. In this case, Lasix gel, ointment, cream, pill, spray, continuous-release, extended-release, Lasix online cod, Mike uses MEDIUMINT(8) to describe the primary key of ab_id in the code.
If you have phpmyadmin (and you should), Lasix no prescription, Doses Lasix work, you can fix this problem rather easily by editing the structure of the table to change ab_id to INT(10) in both the pitches and atbats tables. Additionally, what is Lasix, Is Lasix addictive, you need to change pitch_id in pitches to an INT(10). This will allow for larger numbers to be stored in those rows, Lasix blogs. Lasix from canada, [caption id="attachment_258" align="aligncenter" width="530" caption="phpmyadmin - Where to edit your PITCHf/x database (click for larger)"][/caption]
If you don't use phpmyadmin, the MySQL code to execute at the command line is something like:
ALTER TABLE pitches MODIFY ab_id INT(10);
Good luck with your PITCHf/x database building, comprar en línea Lasix, comprar Lasix baratos. Order Lasix online c.o.d. Where can i find Lasix online. Lasix from canadian pharmacy. Lasix mg. Lasix class. Discount Lasix. Order Lasix from mexican pharmacy. Lasix pharmacy. Lasix without a prescription. Lasix without prescription. Lasix pics. Lasix interactions. Lasix dose. Buy Lasix from canada. Rx free Lasix.
Similar posts: Avodart For Sale. Tindamax For Sale. Lumigan For Sale. Ketoconazole Cream no prescription. Buy Retin-A without a prescription.
Trackbacks from: Lasix For Sale. Lasix For Sale. Lasix For Sale. Comprar en línea Lasix, comprar Lasix baratos. Japan, craiglist, ebay, overseas, paypal. Where can i find Lasix online.


text:
Ariat Kaden Rugby - Ladies, Absolute Green Stripe
5 Closeouts from $22.95
Bright and Stylish Rugby!
The Ariat® Ladies Kaden Rugby Absolute Green Stripe Shirt is a striking, yarn-dye striped jersey. This eye-catching top features rugby construction with a twill placket and collar.
The Ariat® Ladies Kaden Rugby Shirt offers:
Customer Reviews
|Write a Review
|This product has not been rated by any customers. Be the first person to write a review of this product.
$75 Monthly Gift Certificate Prize and a $1000 Gift Certificate End of Year Grand Prize
If you own this product, please write a review for it. The Review should be helpful to other Shoppers and reflect your own experience with this product. Prizes awarded based on the quality of the review - positive or otherwise.
Shop all available Ariat products
25.95 36.95
35.95 49.95
32.95 49.95
More For You
$25.95 $36.95
- Company Info
- About Equestrian Collections
- About our Website
- 100% Satisfaction Guarantee
- Customer Testimonials
- eCatalogs
- Home
- Rewards Program
- Join the Mount Up to Rewards Program
- Rewards for You
- Affiliate Program
- Become an Equestrian Collections Affiliate
- Sponsorships & Fundraising
- Terms of Use
- Privacy Policy
- Terms of Use
- Help
- My Account
- Order Tracking
- Returns and Exchanges
- Shipping Info
- Sitemap
- We Care
- Eco-Conscious Products
- No Paper Catalogs - Save Trees
- Customer Service
- Toll Free: (877) 872-4415
- Help Section
- Contact Us