url() bug
See original GitHub issueWhile using the browser, not node, in dev mode:
.test { background: url(); background: url('test'); background: url(''); }
when “manually invoke the parser and compiler” via JavaScript will output:
.test { background: url(); background: url('test'); background: url([object Object]); }
but when compiled via the ‘rel set to “stylesheet/less”’ method:
.test { background: url(http://www.example.com/less/); background: url('http://www.example.com/less/test');
with the last declaration causing a FATAL ERROR: b.value.charAt is not a function
This might be related to or explain a number of reported issues about “url()” and “string interpolation”
Issue Analytics
- State:
- Created 11 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
URL Parsing-Library Bugs Allow DoS, RCE, Spoofing & More
They occur when a web application accepts a user-controlled input that specifies a URL that the user will be redirected to after a...
Read more >How to Troubleshoot an Error in a URL - Lifewire
Did you type a URL into your browser and find that it doesn't load? You may have the wrong URL or you may...
Read more >JDK-4249722 URL.openStream() throws NULL ptr ... - Bug ID
JDK-4249722 : URL.openStream() throws NULL ptr exception with FTP protocol and .zip file. Type: Bug; Component: core-libs; Sub-Component: java.net ...
Read more >Errors in transforming URL objects back to URLs. #1338
URL objects transforms correctly into strings. What do you see instead? When in ported code, fetch() returns FailedToOpenSocket: fetch() failed ...
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
also @WraithKenny you might reconsider if you really want to be working with a library that has a list like that which hasn’t been addressed in over 2 years.
thanks, but that only half fixes the problem. There is a better patch (I think) to move the calculation after evaluation (after variables have been assessed). I will be looking into this next week.