Can somebody please point out the error in my code?
var myStr = "I am a \"double quoted\" string inside \"double quotes\"."; // Change this line
Otherwise this is a bug. You can see how I have worked through the problem in detail here.
Can somebody please point out the error in my code?
var myStr = "I am a \"double quoted\" string inside \"double quotes\"."; // Change this line
Otherwise this is a bug. You can see how I have worked through the problem in detail here.
Thank you for this response. Honestly, I do not understand what you are saying even as I hear you clearly. Safari runs on a gazillion iPhones from the same code base and this very much sounds like the bad old days of “works best with IE”. I’m old enough to remember that. The browser is up to date as of 2018 and if features really must be so bleeding-edge, perhaps you should dial back a bit.
Listen, I literally love you and what you do. It is revolutionary. I am also saying that this looks awful. Safari is a major browser. What happened to the principles of “graceful degradation” or are we all just eventually going swap over to Chrome/ Blink and become a web monoculture? Microsoft did it, after all. It’s really poor design to tell me to move over to Chrome. I will do it, but what you are telling me blows.
When I remove the commented section, the test succeeds.
Do you care to explain what you think is happening? It’s useful to those of us who want to understand code and the browser on a deeper level than just getting the certification. Also: I am learning a lot by catching the bugs. It forces me to write alternative code to prove what think are mistakes instead of just firing up Chrome.
as it is checking how many backslashes are used, the tests are probably checking the content of the editor. doing this there is no distinction between comments and normal code
Do you have any clues as to the technical reasons Chrome and Safari behave differently?
freecodecamp uses newer technologies that do not yet work on Safari or Edge
I think that’s essentially the same thing as “Google technologies” - so, singular as opposed to newer - and that is bad for the web. The shape of it shouldn’t be determined by an advertising company. Appears to be exactly the same situation back when IE was king and M$ was doing all kinds of proprietary stuff that didn’t work in other browsers. Chrome tracks me/ allows tracking, and tracking is malware. I’m never going to use it again, and users should not be forced to. It’s a very poor decision by freeCodeCamp. Privacy is also a performance issue. From this article:
“Blocking cookies is bad for privacy. That’s the new disingenuous argument from Google, trying to justify why Chrome is so far behind Safari and Firefox in offering privacy protections.”