Resource.textContent() not implementable in Browser
See original GitHub issueRight now Resource.textContent()
isn’t implemented in the Browser (nor is .size
obviously) because in the browser we can only deal with external data asynchronously.
Right now that means that a module like ceylon.locale
cannot be used at all in a browser.
Futures aren’t part of the language module so it seems to me that the only thing we can do is to add asynchronous versions of the two members:
textContentAsync(encoding, callback)
andsizeAsync(callback)
The documentation should then state that it would be preferable to always use those for best compatibility across all possible platforms.
Wdyt @gavinking @chochos ?
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:25 (25 by maintainers)
Top Results From Across the Web
'innerText' works in IE, but not in Firefox - Stack Overflow
Update: I wrote a blog post detailing all the differences much better. Firefox uses W3C standard Node::textContent , but its behavior ...
Read more >Text content that changes automatically can be paused ... - W3C
This rule checks that for any text content that regularly changes automatically, there are instruments to pause, stop, or hide it or to...
Read more >The poor, misunderstood innerText - Perfection Kills
Few things are as misunderstood and misused on the web as innerText property. That quirky, non-standard way of element's text retrieval, ...
Read more >Node.textContent - Web APIs | MDN
The textContent property of the Node interface represents the text content of the node and its descendants.
Read more >A JavaScript implementation of innerText (not innerHtml) for ...
In the sick, twisted word of cross-browser DOM-based JavaScript, sometimes you ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have some rubbish heuristics for that in the code already.
How do we detect text files?