Comments (3)
What do we mean by "safe" here? If we allow treating a bound string as markup, there's not much safety to be had. Off the top of my head the main safety to be had would be if we allowed binding to some constructed DOM hung off the model (sort of a model-as-template). Or is there something else we can do?
from webkit.
Abarth's original plan about this sort of mirrored the approach that ruby
takes which is to allow markup to be evaluated, but limited by a policy in
what constructs can be contained in the markup.
It's possible that this is an orthogonal, but related primitive that we
need to raise. In any case, it seems like it's a requirement that there by
some mechanism for achieving this.
On Wed, Aug 29, 2012 at 10:17 AM, Adam Klein [email protected]:
What do we mean by "safe" here? If we allow treating a bound string as
markup, there's not much safety to be had. Off the top of my head the main
safety to be had would be if we allowed binding to some constructed DOM
hung off the model (sort of a model-as-template). Or is there something
else we can do?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-8133366.
from webkit.
Ah, right, like "only and tags allowed". Does sound like a primitive missing...
from webkit.
Related Issues (19)
- Implement DOM stability for iteration
- design formal delegate API
- need the ability to reference "this" and ancestor values within bindings HOT 1
- non-string model values cause crashes in v8::Value::toString HOT 1
- Avoid memory leaks by holding the .model and .modelDelegate properties in the JS wrapper
- Provide an API on Element and Text to get a list of bindings HOT 5
- Add synchronous API to HTMLTemplateElement for template instantiation HOT 1
- added .model and .modelDelegate to ShadowRoot HOT 1
- Error in Source/WebCore/mdv/ScriptValueBinding.cpp HOT 1
- Wrong check for text binding
- re-hookup innerHTML for HTMLTemplateElement HOT 2
- ref needs to look in template owner document too HOT 5
- Attempt to implement better cloneNode(true) behavior for templates
- removing a template element should cause its instances to be removed HOT 2
- design how model values propagate into shadow dom HOT 3
- implement <template instantiate/iterate ref> HOT 1
- need tests asserting that parser-created templates function properly HOT 1
- design context-aware bindings HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from webkit.