It looks like the png is getting word wrapped. Line spacing is so large that the png on the second line is getting pushed into the space of the icon below, and the icon below is given a higher Z value, so it goes over it. The different font has a different letter width and can influence the line spacing by being taller than the original font.

See if you can find an option to reduce line spacing or an option to increase icon spacing (vertical or horizontal). I would expect these to be advanced settings though. Iirc, most Linux desktops don't use ellipses on long names, like some other operating systems (macOS iirc).

Yes. I'm not sure what you think makes you bad at writing bug reports, but here are tips I give to everyone (my day job involves working with bug reports).

Nominally, a decent bug report should have:

• the steps that got you the bug
• whether you can reproduce the bug
• what you expected to happen instead of the bug

Doing any of these things makes bug reports so much more actionable. You can do it. I believe in you!

Edit: Including a contact method so the software developer can have a conversation with you can also be helpful but not strictly required. Some bug reporting methods do this implicitly, like email bug reports and GitHub issues.

It's exactly this. The policies put in place by "healthcare administrators" (MBAs and such with healthcare flavoring, not people that actually know how to care for people's health like doctors and nurses) are designed to process the most patience in the least amount of face time possible, so that each doctor and nurse can see more patients per day, meaning more office visit fees, meaning higher profit. My dad calls it the "cattle shoot" and I feel that's a pretty apt analogy. It's the same general reason that fast food restaurants and pharmacies and department stores are perpetually understaffed: fewer staff members means lower "overhead" costs.

Linking outside of their website would reduce engagement, thus ad revenue. I'd put money on this is why so many news sites rarely link out anymore.

This is called "Embrace, Extend, Extinguish". Microsoft coined the term internally for their responses to open standards in the 90's and 00's.

https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

Correct. In the US, these practices are commonly not paid by employers.

The requirement should be that any time an employer makes a demand of an employee's time, they pay.

FA waiting on your plane to arrive that's 6 hours late? Pay up.

15 Apple store employees lined up and waiting to get searched by a single manager after a shift? Pay up.

Require an employee to respond to phone calls or issues after hours? That's not "after hours", that's hours. Pay up.

Make an employee commute to an office for a job that can be accomplished from home? Believe it or not, pay the hell up.

Making demands of a person's time for a job is part of the job. They should be compensated for it.

Second. John Barnett was the first in early March.

Yup. FCC abandoning the Fairness Doctrine under Reagan is what brought us sensationalism in broadcast news. Instead, it should have been expanded to cover anything using the term like "news" and "current events", similar to other protected terminology like "professional engineer". Cable news never being covered by FD was also ridiculous.

More info: https://www.snopes.com/fact-check/ronald-reagan-fairness-doctrine/

When has being ineffective ever disqualified someone from Congress?

... I started writing this reply to be funny, then I realized it's basically true, then I got sad.

Yes.

https://www.cnn.com/2024/02/23/us/alabama-ivf-embryos-supreme-court-ruling-legislation/index.html

Lots of discussion here of Zed being macOS-only. Multiplatform support is being tracked in this issue for Linux, Windows, and web:

https://github.com/zed-industries/zed/issues/5391