csuwldcat

11 ms·

61.
Element Queries, From the Feet Up(backalleycoder.com)
6 points by csuwldcat 12y ago|1 comments
62.
by csuwldcat 13y ago
This is a mechanism for all web apps - even 100% clientside, packaged apps - to do crypto-currency payments using the emerging Web Activity API. The API is supported in Firefox OS, and will soon be available in the Firefox browser on deskto
63.
Clientside App Crypto-Currency Payments with Web Activities(docs.google.com)
7 points by csuwldcat 13y ago|2 comments
64.
by csuwldcat 13y ago
XUL is only used for the external chrome interface of the Firefox desktop browser, let's be clear not to commingle the technology used to build the UI of Firefox with the standards-based technologies that power web apps/pages ;)
65.
by csuwldcat 13y ago
Sad that this PSA even needs to be written, but alas: * NO, open web apps that run on Firefox and Chrome are in no way linked to non-standard markup languages like XUL. * Please disregard any users who have made this fallacious assertio
66.
by csuwldcat 13y ago
When you say: "(2) stick to standards (e.g., using HTML now instead of XUL)" and "(3) if your system isn't getting traction, retry in 10 years?" It sounds like you are claiming Mozilla is promoting the use of XUL as
67.
by csuwldcat 13y ago
Support is already under way for slider in Firefox, and the rest of the input elements are in development. Why don't you contribute to the project instead of shooting off crass remarks about what "other people", "those p
68.
by csuwldcat 13y ago
The problem is, there isn't anything else kinda similar - Web Components will enable things that are impossible for libs like jQuery Mobile and jQuery UI to do presenting (with any degree of sanity). The Web Component APIs will also al
69.
by csuwldcat 13y ago
We for starters, this entire component package is lighter than some single jQuery UI plugins. It is declarative, something jQuery UI simply cannot do as it is designed. Web Components APIs are landing in browsers, so these code paths will b
70.
by csuwldcat 13y ago
Yes, Brick is a set of components developed with X-Tag (the web components sugar library)
71.
by csuwldcat 13y ago
Polyfill != works back to the stone age, it just means providing backwards compatible functionality. Aside from that, there are some polyfills that aren't even technically possible, or would destroy performance, in older browsers
72.
by csuwldcat 13y ago
Your comment is misguided for a few reasons: Under your logic, any compilation of functionality can be reduced to vanilla, long-hand, zero-abstraction, blocks of HTML, CSS, and JS functions --> Ok everyone, dubcanada has figured out that
73.
by csuwldcat 13y ago
Each component is isolated in just the way you describe, the only requirement is the base X-Tag Web Component library.
74.
by csuwldcat 13y ago
The issue might be locality dependent, we have several people where who are running the exact same version and platform that cannot reproduce - could be an issue like this: https://github.com/eternicode/bootstrap-datepi
75.
by csuwldcat 13y ago
Given that the errors and ability to reproduce are so erratic (to the extent that people with the very same browser versions on the same platform are seeing different behavior), I have a feeling the issue may be something like this: https:
76.
by csuwldcat 13y ago
I believe you are describing the native datepicker , I am seeing the same weirdness. Be advised, the calendar polyfilled calendar is only active when a native implementation is not detected, or you force it to be used. This may be a bug in
77.
by csuwldcat 13y ago
I'm also running Chrome 28 (Version 28.0.1500.95) on Windows, but everything is running fine. I'm wondering if Chrome itself is locking up, because the calendar demo is has only one demo of the polyfill picker, the rest are the na
78.
by csuwldcat 13y ago
Underlying Polymer's opinionated framework, there is a set of polyfills for the emerging Web Components standards - both Mozilla's X-Tag library and Polymer use these polyfills as the basis of their offerings.
79.
by csuwldcat 13y ago
The folks working on the components are going to be incorporating all this feedback and reporting going forward. Everyone is encouraged to file bugs with the repo here: https://github.com/mozilla/brick/issues Just
80.
by csuwldcat 13y ago
You're overlooking that the underlying technology - Web Components - is landing as a standard as we speak in both Firefox and Chrome. The idea that creating custom elements is inherently bad is an urban legend - there is no empirical b
81.
by csuwldcat 13y ago
"How would I implement an offline navigation? (which is currently really not possible in JavaScript)" - wow, just wow. Beyond the fact that this is just plain wrong - there are packaged apps that ship all assets on install, as wel
82.
by csuwldcat 13y ago
"Ignoring the housing bubble"...great talking point, but sadly, inaccurate. The most significant obstacle that blocked attempts by the Bush administration to combat the runaway housing/financial sector bubble was a Democratic House that str
83.
by csuwldcat 14y ago
The release cycle should be quite rapid, more so than any of the the existing OS platforms on the market. Additionally, if you can develop web sites/apps well on "evergreen" desktop browsers like Firefox and Chrome, the experience will be a
84.
by csuwldcat 14y ago
There are a multitude of natively available browser functions that are immutable and cannot be CRUD'd. This guy really needs to understand more about the browser. His commentary on client storage in the browser also is myopic.
85.
by csuwldcat 14y ago
"Bind it like this: $( '.datepicker' ).datepicker()" - so the very first instruction is an incorrect reference to JavaScript 'binding' as something that extends or provides features to an element, vs what it truly does: change the scope ref
86.
by csuwldcat 14y ago
Just one little citation of the original article that demonstrated this hack would be nice. The guy references David Walsh's blog (a friend of mine), who even in the article cites and attributes the method, yet doesn't include it in here? J
87.
by csuwldcat 14y ago
Hey whatdayaknow, the method I created! Here's a follow-up I published a while back that provides an generic listener method using the technique: http://www.backalleycoder.com/2012/08/06/css-selector-listen...