What is triald and why is it taking so much disk space?
eclecticlight.co
What is triald and why is it taking so much disk space?
1–10 of 295 posts
Re: What is triald and why is it taking so much disk space?
#2[deleted]
Re: What is triald and why is it taking so much disk space?
#3No post body was provided.
Re: What is triald and why is it taking so much disk space?
#4Howard Oakley is such a prolific writer on newly appearing macOS issues. Take for example this piece. It's collecting new information and trying form a picture, and that's how the community starts learning. Awesome content.
Re: What is triald and why is it taking so much disk space?
#5Remember when operating systems didn't have multi-gigabyte binary blobs performing cryptic actions with an extremely chatty online connection?
Re: What is triald and why is it taking so much disk space?
#6Open source is where you don't have to apply guesswork to find out what a suspicious looking piece of software is doing on your computer.
Re: What is triald and why is it taking so much disk space?
#7The drop cap at the start of the article, is capturing pointer-events. Adding pointer-events: none; will make people who read by selecting text with the mouse happy.
.single .entry-content:before { pointer-events: none; }
Re: What is triald and why is it taking so much disk space?
#8Jesus I hate being A/B tested without my consent. Particularly, why is Apple of all places doing this, given their otherwise strong track record of standing up for their users in regard to tracking and other bullshit by major players?!
Re: What is triald and why is it taking so much disk space?
#9I trust that Apple isn't doing anything nefarious here, but at the same time, I'm quite grateful that others aren't so trusting. I want the "white hat" suspicious and skeptical rooting through everything. In fact, I don't think I'd trust Apple so much if it weren't for those that don't trust them. Their constructive distrust enables my trust.
Re: What is triald and why is it taking so much disk space?
#10The drop cap at the start of the article, is capturing pointer-events. Adding pointer-events: none; will make people who read by selecting text with the mouse happy. .single .entry-content:before { pointer-events: none; }
I suspect that the browser you are using is not spec-compliant. Pseudo-elements (like ::before and ::after) are not actually present in the DOM and are therefore not selectable.
edit: I see that you are probably referring to the z-index of the ::before element overlapping the text, preventing selection.