Awesome. Now I think I understand the full picture you described.
When trying to offer a feature that is still being specced, prefix the specced
APIs, and once the spec is stable, for browsers that don't ship these APIs,
alias the prefixed ones by dropping the prefix. Is that correct?
On Aug
On Aug 6, 2015 11:05 PM, Glen Huang curvedm...@gmail.com wrote:
This assumes you'll match
That's a good point. I agree for most APIs it's probably better to simply
use polyfill code for all browsers. But some APIs have some extra benefits
that might not be polyfillable. For example, the
This assumes you'll match
That's a good point. I agree for most APIs it's probably better to simply use
polyfill code for all browsers. But some APIs have some extra benefits that
might not be polyfillable. For example, the native version of web animations
happen in a compositor thread, so
On Thu, Aug 6, 2015 at 6:50 PM, Glen Huang curvedm...@gmail.com wrote:
@William @Matthew
Ah, thanks. Now I think prollyfill is prolly a good name. :)
@Brian
Actually, I had this pattern in mind:
When no browsers ship the API:
```
if (HTMLElement.prototype.foo) {
@William @Matthew
Ah, thanks. Now I think prollyfill is prolly a good name. :)
@Brian
Actually, I had this pattern in mind:
When no browsers ship the API:
```
if (HTMLElement.prototype.foo) {
HTMLElement.prototype._foo = HTMLElement.prototype.foo;
} else {
HTMLElement.prototype._foo =
'Prolly' is a slang term for probably... At least in the US it is.
On Aug 5, 2015 11:00 PM, Glen Huang curvedm...@gmail.com wrote:
Thanks for the detailed explanation.
The only thing I'm not sure I understand is the pattern you described:
```
HTMLElement.prototype.foo =
Question all,
Is web remoting web socket built in HTML 5 and above/
Why do we need XMLHttpRequest at all?
Pls. enlighten me.
I am not sure if we should be bothering about
XMLHttpRequest.
L.Mohan Arun
@cintanotes2
I want to write/proofread from home.
On Thu, Aug 6, 2015 at 5:49 PM, Matthew Robb
Because it will probably become a real polyfill.
Em Thu, Aug 6, 2015 às 4:00 AM, Glen Huang curvedm...@gmail.com escreveu:
Thanks for the detailed explanation.
The only thing I'm not sure I understand is the pattern you described:
```
HTMLElement.prototype.foo = HTMLElement.prototype._foo;
Thanks for the detailed explanation.
The only thing I'm not sure I understand is the pattern you described:
```
HTMLElement.prototype.foo = HTMLElement.prototype._foo;
```
I had this pattern in mind when you talked about prollyfills:
```
HTMLElement.prototype._foo = function() {
if
Do polyfills like WebReflection's DOM4 look promising?
No. Lets choose to not spoil a text-based markup language by trying to
emulate geometry. etc. There are other tools for geometry. HTML not suited
for geometry.
'I feel it's more sustainable to bet on spec APIs.'
No. I prefer lets Focus on
On Tue, Aug 4, 2015 at 8:22 PM, Glen Huang curvedm...@gmail.com wrote:
There's actually a lot of questions in here, so let me take them one
at a time...
On second thought, what's the difference between prollyfills and libraries
A major difference is that it's hard to translate libraries into
On second thought, what's the difference between prollyfills and libraries
exposed web APIs in a functional style (e.g., node1._replaceWith(node2) vs
replaceWith(node2, node1)? Or in a wrapper style like jquery does? Prefixing
APIs doesn't seem to be that different from using custom APIs? You
Brian,
prollyfills seems pragmatic. But what about when the logic of an API changes,
but not the name? The node.replaceWith() API for example is about to be
revamped to cover some edge cases. If the prollyfills exposed
node._replaceWith(), what should it do when the new node.replaceWith()
On Mon, Aug 3, 2015 at 9:07 PM, Glen Huang curvedm...@gmail.com wrote:
Brian,
prollyfills seems pragmatic. But what about when the logic of an API changes,
but not the name? The node.replaceWith() API for example is about to be
revamped to cover some edge cases. If the prollyfills exposed
On Sun, Aug 2, 2015 at 9:39 PM, Glen Huang curvedm...@gmail.com wrote:
I'm pretty obsessed with all kinds of web specs, and invest heavily in tools
based on future specs. I was discussing with Tab the other day about whether
he thinks using a css preprocessor that desugars future css is a
15 matches
Mail list logo
