@wilto @etportis @beep @firefox @mozilla @adactio @jensimmons @keithjgrant @paulhhowells @rachelandrew @FullStack_Jimmy @brkemper @ZeeCoder @innovati @elrond25 +listening. Appreciate blogs & frankness re: momentum Retry in #WICG? →GH: https://github.com/ResponsiveImagesCG/cq-usecases/issues/44
Retry in #WICG? →GH: https://github.com/ResponsiveImagesCG/cq-usecases/issues/44
@innovati @jensimmons @FullStack_Jimmy @ZeeCoder @keithjgrant @firefox @mozilla @paulhhowells @rachelandrew @brkemper appreciate links, updated proposal! RICG waiting on requirements proposal from March? https://github.com/ResponsiveImagesCG/cq-usecases/issues/36#issuecomment-287917442 cc @wilto @beep Important step (before syntax arguments) to capture both broader use-cases and implementation constraints. cc @davidbaron And as far as “have the ears of the browser makers”, several on this thread work at browser makers. I’m seeing high interest, but this needs more active community participation (like back & forth interactions), perhaps some wrangling.
RICG waiting on requirements proposal from March? https://github.com/ResponsiveImagesCG/cq-usecases/issues/36#issuecomment-287917442 cc @wilto @beep
Important step (before syntax arguments) to capture both broader use-cases and implementation constraints. cc @davidbaron
And as far as “have the ears of the browser makers”, several on this thread work at browser makers.
I’m seeing high interest, but this needs more active community participation (like back & forth interactions), perhaps some wrangling.
@keithjgrant @jensimmons @firefox @mozilla @paulhhowells @rachelandrew @FullStack_Jimmy @brkemper @ZeeCoder @innovati container queries / element queries certainly sound powerful+useful. Yet https://github.com/ResponsiveImagesCG/container-queries/ untouched in 2+ yrs. See also comment by @davidbaron and thread: https://github.com/ResponsiveImagesCG/container-queries/issues/3#issuecomment-185951645 Perhaps worth figuring out pre-requisites.
Yet https://github.com/ResponsiveImagesCG/container-queries/ untouched in 2+ yrs.
See also comment by @davidbaron and thread: https://github.com/ResponsiveImagesCG/container-queries/issues/3#issuecomment-185951645
Perhaps worth figuring out pre-requisites.
@ManuelBieh @firefox @mozilla thanks — I agree better print support would be good, both in general, and with new paged features. Lots to do there and may take longer. Track our status on the #CSS Paged Media Module here for starters: https://bugzilla.mozilla.org/show_bug.cgi?id=286443
@filtercake @topaxi by mixins do you mean @-apply rule as proposed by @TabAtkins: https://tabatkins.github.io/specs/css-apply-rule/ or another approach? Looks useful but quite challenging to get right. First step would be to get @CSSWG to start exploring it.
Looks useful but quite challenging to get right.
First step would be to get @CSSWG to start exploring it.
@asinnema @kriesse @Mozilla It appears @Firefox supports hyphenation with a Dutch dictionary (among others) since Firefox8 (2011), see: https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens#Browser_compatibility Is there a particular page or CSS that is not working?
Is there a particular page or CSS that is not working?
@bdc @alanstearns @firefox @mozilla thanks for the suggestion. Follow along with our progress on SVG geometry properties in CSS here: https://bugzilla.mozilla.org/show_bug.cgi?id=1383650 cc: @heycam
@octothorpe @rachelandrew @firefox @mozilla thank you for letting us know! Try out @FirefoxNightly and report back! And thanks @dietrich for the bug link. Follow along more CSS Values & Units here: https://bugzilla.mozilla.org/show_bug.cgi?id=741643
And thanks @dietrich for the bug link. Follow along more CSS Values & Units here: https://bugzilla.mozilla.org/show_bug.cgi?id=741643
Blending cache and live responses in order to achieve response time goals.
I’m in the process of converting four Whimsy applications from React.js to Vue; and I’m taking a moment to jot down a list of things I like a lot, things I find valuable, things I dislike (but can work around), and things I’m not using.
On balance, so far I like Vue better than React.js (even ignoring licensing issues) or Angular.js, and am optimistic that Vue will continue to improve.
the current implementation is a lot more fun to develop and easier to maintain than prior versions. As an example, if it were decided that the moment the secretary clicked the ‘timestamp` button on the 'Call to order’ page, all comment buttons are to be removed from all windows and all comment modal dialogs are to be closed, this could be implemented using a single if statement as the event is already propagated, and a re-render is already triggered. All that would be required is to change the conditions under which the comment button appears.
The board agenda tool has been tested on Linux, Mac OS/X, Vagrant, and Docker. It contains a suite of tests.
I replaced IE results with Spartan results in my urltests. Other than the user agent string, nothing changed.
Following are selected examples where three out of four of the top browsers agree, identified by the odd browser out:
I’ve released Ruby2JS version 2.0. Key new features:
The Whimsy Agenda rewrite-in-progress (previously based on Angular.js, now being rebased on React.js) can be used to explore both of these features.
The second demo is a calendar. Unlike the tutorial which is a single file, this application is organized in a manner more consistent with how I expect projects to be organized.
Jeremy Ashkenas: “work towards building a language that is to ES6 as CoffeeScript is to ES5”… close, but—do it for [ES6+HTML+CSS], and you’ll win ;)
It occurs to me that there is a shortcut available. Let a library like React replace [ES6+HTML+CSS]. Then build a DSL for that library.
Brian Leroux: ES6 and Web Components
My take is that this talk lumps React in with others based on when it was introduced; but that it is fundamentally different from, say Angular.js as Angular.js is from jQuery.
I have test results that show that there is much work to be done.
The most likely path forward at this point is to get representatives from browser vendors into a room and go through these results and make recommendations. This likely will happen in the spring, and in the SF Bay Area. With that in place, I can work with authors of libraries in popular programming languages to produce web-compatible versions. This work will take the form of bug reports, patches, or — when required — authoring new libraries.
My original intent was to aggressively prune unnecessary function with the intent of producing a more maintainable result, but with the ability to have automated acceptance tests, this is now less of a concern.
I particularly like the comment that “It just works” was never completely true. My experience is that when working with open source codebases, doing so on an Linux operating system comes much closer to “It just works” than doing so on any other.
Not rack’s fault, but Sinatra hasn’t released in a while. Problem has been known since July, and a fix was merged into master in August. One possible workaround has been posted. An alternate workaround:
module Rack class ShowExceptions alias_method :old_pretty, :pretty def pretty(*args) result = old_pretty(*args) def result.join; self; end def result.each(&block); block.call(self); end result end end end
I’ve clearly been neglecting my little spot on the web.
It has gotten so bad that Brendan Eich had to link to a web archive copy of a page of mine. I must say, however, that it is very ironic and amusing that it is was that particular page. General outline of my current approach:
With IE9 now released, we want you to serve IE the same markup as you do for other browsers, and make sure your site works great running in IE9 standards mode. We recently blogged about preparing your site for IE9, and you can check out the Internet Explorer 9 Compatibility Cookbook for lists of changes that may impact your site or the Internet Explorer 9 Guide for Developers for a more complete list of what's changed. Today we are introducing a new resource that can help speed up the process of preparing your site: Compat Inspector.
About Compat Inspector
Compat Inspector is designed to help sites migrating to IE9 Standards Mode, not those running in legacy modes. You may still need to refer to the above documentation for some issues. The best pattern is to use Compat Inspector first, then fall back to the documentation if nothing is found.
How do I use it?
To use Compat Inspector, add the following script before all other scripts on each page you want to test:
Note: If you have Fiddler, you can automatically load Compat Inspector on all pages you visit by adding this snippet to your FiddlerScript (which is particularly helpful if your page uses frames). I recommend installing the FiddlerScript Editor extension if you don’t already have it.
After you have the above script in place, open your page in IE9 and start using it. Explicitly test any interactions known to be working incorrectly (only executed code is analyzed). Compat Inspector will keep a running total of all errors and warnings associated with detected issues. A summary view in the upper right hand corner of the page displays the results:
Click on this view to expand it and obtain detailed information about each detected issue with links to relevant documentation:
Most errors and warnings also provide two additional actions for further investigation: "Verify" and "Debug."
Some test cases have built-in "verifiers" that emulate legacy behavior. This allows you to confirm the root cause of an issue before making any changes to your code.
Prerequisite: Compat Inspector is opened in the detailed information view and displaying an error or warning message containing a checkbox labeled "Verify."
Compat Inspector can also help you isolate where in your code things went wrong via the "debug" feature.
Prerequisite: Compat Inspector is opened in the detailed information view and displaying an error or warning message containing a checkbox labeled "Debug."
How does it work?
Compat Inspector uses features introduced in IE9. At its core, Compat Inspector overrides native APIs using ECMAScript 5th edition getters/setters and depends on the browser to correctly expose APIs per WebIDL. Compat Inspector then uses these overrides to track interactions between the page and the native platform. This allows it to report issues at runtime as the problem code is executed.
The rest of the Compat Inspector infrastructure makes use of various other new features as needed. Some examples include DOM Level 3 Core APIs, DOM Level 3 Events APIs, and CSS3 Border Radius. Compat Inspector also depends on features introduced in IE8 such as HTML5 Local Storage, HTML5 Cross-Document Messaging, native JSON support, and Selectors API.
My site works, now what?
Remove the Compat Inspector script from all your pages before publishing. Compat Inspector is a test tool and should not be used in production. After that, keep an eye on the IE blog; we may have new test cases to share in the future.
—Tony Ross, Program Manager, Internet Explorer