@whipdancer
Weeks of coding and can save you hours of planning.
Nothing here yet.
Nothing here yet.
Just an aside, I no longer study music but I still love the topic. I found a video from the World Science Festival on music and the brain very interesting. One of the things I learned a tiny bit about is the difference between scales in western and eastern cultures. I'm including a link to the part of the video where the subject is discussed. Notes and Neurons: In Search of the Common Chorus
I consider them to be two ends of a path. If you are going through a neighborhood and see the path leading from the road to the door of someone's house, you can consider that an event. addEventListener the way you mark the path (or in this example the house you want to visit) the you are interested in. Your browser will raise an event in response to something... scrolling, clicking, navigating, etc. In order for code that your write to 1) know about those events 2) respond to those events, you have to listen for them. addEventListener is a way you can do that.
Mocks are instantiations of real object in your system, complete with all the necessary plumbing and expected functionality of that real object. I will use a mock API endpoint (an instantiation of a real API endpoint that doesn't actually affect other systems/data) that responds appropriately to a given input (i.e. returns an error, returns the expected object). Stubs are incomplete. I use stubs to fake something that I don't know exactly what it needs to be, yet. I frequently will create stub API end points that are only designed to return a canned response, while I figure out what I actually need from the API I have yet to build. To put it another way: A mock is a fake based on something that actually exists in your system or application. A stub is a fake based on something that either does not exist in the necessary state, that you do not need actual business logic of, or a place holder until other code is completed.
I've found 2 different references for the removeAttribute method. The most common reference indicates only requiring the attribute name. The other reference includes a second, optional parameter of value 0, 1 or 2. Given that I don't know which is canonical (or if canonical even exists), my default will almost always be to use the MDN documentation (which does not reference the optional parameter). The optional parameter does not fail when I try it in JsFiddle, or my browser. Can you elaborate on the issue? Is the version with the optional parameter deprecated? Was it proposed and not formally adopted? I was not able to find a definitive answer.
Sounds like the issue is a d**k-head salesman, not a cyber-squatter (assuming they are not one and the same), whose primary interest is pumping up his commission, not closing the sale. I do generally agree that unless your brand is at stake, paying the premium is probably not a good idea.
I already donate because they are among a select few that are actually trying to improve the web. Basically... Mozilla is one of the "Good Guys". I will support them with a monthly subscription if the features are something of value for me. I will also continue to donate to the .org for as long as their mission remains altruistic in nature.