No Stupid Questions
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
If there are obligations, Firefox is such a fringe user agent these days that they can probably go without supporting it. The 3.8% of Swedes not using Chromium or Safari will fall off any serious compatibility requirements.
I doubt anything will break in Firefox, though. They just don't want the burden of having to support a few hundred people when Firefox implements a feature slightly wrong/non-standard/not at all.
Just to be pedantic: we've had a hell of a time implementing dynamic resizing of svg's in Firefox. Works fine with Chromium. We spent far too much development time to keep our 4% of users happy, but eventually we did it. Perhaps newer versions of Firefox changed this, but there are customer-facing oddities the bank's customers may experience.
I've had similar issues with getting CSS tables to lay out properly in Chrome. Worked fine in IE/Edge/Firefox/WebKit but Chrome just randomly threw a fit and rearranged items for no reason, even the Javascript engine agreed with me that the tables should look like they were supposed to but they just didn't when rendered.
My experience with SVGs in Firefox is that Firefox supports pretty much every basic features, but it expects the SVGs to be up to spec. As it turns out, a lot of SVGs on the web rely on quirks and side effects and you only find out they're technically invalid when digging deep into the spec. Them behaving differently whether or not there's an img tag around them also doesn't help, and I've run into a few files using SVG features that only worked in some Adobe product and Chrome (only on desktop, IIRC) .
Getting browsers to work consistently still sucks, even when it's not nearly as big a problem as it was fifteen years ago. I totally get why people don't test for Firefox. We didn't use to test for Safari for the very same reason; practically none of our end users used it and there are no usable cross platform browsers to test with even if they were, so we'd probably tell them to download Chrome anyway. Safari mostly worked well enough that if someone decided to pull out an iPad during demos it didn't completely fail and that was food enough. Firefox only worked because devs preferred its superior web development tools.