Pretty sure I only actually saw it being used by Google anyways. I love it for native applications on Android, but couldn't care less about it on the web.
Why in the world was marquee removed? It probably does a better job at scrolling than CSS. Look at everything that had to be written just to mimic a fraction of its power!
To make it efficient, you'd also have to add and remove elements out of sight to save memory. Pure CSS doesn't do that.
Asking just because I'm curious... why are you using xpath?
Also, is this for a website you control or for some else's website?
If you're rendering the page (in a browser, e2e test-runner, spider bot, etc...), have you considered running some js on the page to get the image? Something like: const imagePath = document.getElementById('exampleIdOnElement').style.backgroundImage
Asking just because I’m curious… why are you using xpath?
I'm using a service called FreshRSS that automatically fetches RSS feeds. It has a feature that allows you to create custom feeds for sites by scraping the HTML with user specified XPath expressions.
I know that this isn't exactly "web development", but it uses webdev tools, and I wasn't entirely sure where else to post this.
If you’re rendering the page (in a browser, e2e test-runner, spider bot, etc…), have you considered running some js on the page to get the image? Something like: const imagePath = document.getElementById('exampleIdOnElement').style.backgroundImage
JS is, unfortunately, not possible here. I can only use XPath expressions.
For decades, outsourcing was happening to India and other east asian countries to cut costs. This happened even under low interest rate for loans.
Now that interests are higher the cost cutting and outsourcing only increase.
My own feelings are that we really should figure out if we want to work for such lowballers who cut us off like parasites at the first sign of trouble.
It would be prudent for workers to seek work in smaller, private companies. While they have the risk of going bust... they're hopefully not laying off people in the same breath as announcing record growth.
I looked at the waterfall and I realised I had some design images in there at 2500+ resolution that were taking 5s to load and that was interfering with the loading of the JS.
Thanks, I'll make sure to check this tab first before posting next time.
Web accessibility isn't just about compliance; it's about creating digital experiences that empower and include every user, regardless of their abilities.
I get that it's hard to come up with a good example of using <base>, but I wouldn't show a user-hostile example before ... cutting the element from Chapter 1 entirely. The only time I've ever used <base> was when I had to deploy multiple versions of a multi-page static site to a subdirectory for its staging environment, but to the public root for the production environment. Even then, the solution wasn't, "use <base>," it was, "sort shit out later with nginx."
Step 2: confuse the use case of anchors and buttons.
I understand that it's just an example but it's never just an example. Use appropriate landmarks or break your snippets down to the point where it's obvious that what you're pointing out isn't the whole thing. You don't need <body> or <ul> or <li>, just split the snippet in two, like this:
Don't do that. I mean, don't really do any of this example, but really don't do this last part. Adding class="native" is as cumbersome as adding target="_blank", while also being more brittle. [I edited out a considerable amount of swearing here.] I think this is just a symptom of a bad example gone way too far.
If the client insists on opening all external links in new tabs, get it in writing and then do this:
<base target="_blank" />
let external_links = document.querySelectorAll('a[href^="http"]');
external_links.forEach((external_link) => {
external_link.setAttribute('target', '_blank');
});
You can use querySelectorAll with a prefix attribute selector like 'a[href^="http"]' instead of a typical class selector. This lets you grab all the anchors with hrefs that start with "http" without adding extra syntax where it doesn't really belong. Once you've got your external links, iterate through that NodeList with forEach and tack on target="_blank" using setAttribute. That way, you're not re-implementing default behavior, you're only mildly annoying users with HCI devices, and if JS gets blocked all your links suddenly behave predictably.
Even this is bad! Just don't! It's so easy to not!
Other notes
You should probably start by explaining what an element is, then what an attribute is, then what a value is. Vocabulary is extremely important.
When referencing elements, include the chevrons in the inline style. <meta> vs meta. If they have to guess, they'll guess wrong. Suffix with "element" to really beat them over the head with it.
When referencing attributes, try to keep their values attached. class="foreign". If you can't, suffix it with "attribute."
When referencing values, keep those quotes! "false".
If it's a book about HTML, don't use JS. At all. Every time you reach for JS, stop. Like if you are about to write a self-invoking function to go and find invalid values of the rel attribute, for example, maybe don't.
Thank you for the great feedback! This is one of the benefits of undertaking a project such as this in the open. I hear you with the <base> element. I was in two minds whether I should even include it. I am thinking now that I should, but introduce it merely for completeness and recommend not using it. I wonder if it will ever be deprecated.
SNEED FEED SNEED'S CHUCK FOR FREE FLOYD HOT POCKETS CHUCK'S FLOYD CLEAN IT UP CITY SLICKER CHUCK'S CLEAN IT UP SUCK FEED JANNIES CITY SLICKER SEETHE CITY SLICKER CLEAN IT UP DILATE SEETHE DILATE SEETHE FUCK SNEED'S I CAN'T SUCK FLOYD FLOYD HOT POCKETS COPE SNEED'S FOR FREE CHUCK'S FLOYD COPE SUCK FUCK SNEED CITY SLICKER I CAN'T FLOYD SEED DILATE SUCK SUCK SNEED SNEED'S JANNY
Web Development
Top