Closed ronco closed 8 years ago
I think the best bet is to add a failing test to Ember.js. We can see that PR fail, then merge this fix and cut a new release, then see the PR pass and then merge the bumped version into Ember.
Fix looks good btw.
Will also need to be fixed in tildeio/glimmer
Still needs to be done in tildeio/glimmer, if we forget this it will regress...
@rwjblue yes, @tomdale is going to follow up with @chancancode to get some direction there.
According to @chancancode the work has not yet started on the Node.js-compatible DOMHelper
, what's the best way to track this?
The node version of protocolForURL was throwing an exception if the url is undefined here. This is invoked in sanitizeAttributeValue. This was calling issues for bound attributes with no value in FastBoot environments.
This PR returns a sensible default (
:
) fromnodeProtocolForURL
when theurl
argument is a non-string.I'm not sure how to test this though. I'd like to get a test in place if possible before merging.
/cc @tomdale