No, you make it function properly before I consider “[giving] it a chance”. Firefox is ridden with decade-old compliance bugs, and is generally a pain to write applications and documents for. That's just part of why web applications and documents work worse in Firefox than they do in Chromium. Mozilla should derive from Chromium, if they want to actually deliver a web browser worth choosing. They can even fight their…
I still have issues with Blink's CSS columns 7 years later, so this isn't a one-sided deal.
Like I said, I think Mozilla could put themselves in a great position to differentiate themselves on quality or any other important axis if they would just give up on maintaining Netscape. At this point they don't even support any of the old plugin or extension interfaces, so even if they wanted to rebuild all of their current UI gimmicks, it wouldn't be a crazy amount of work.
As it stands, the least you could say between the two, regarding implementation quality, is that Firefox is almost not noticeably worse most of the time. That's not a terribly high standard.
The an example of the sort of differentiation users appreciate, unbreaking content blockers like uBlock Origin with a patchset that forces Google to either merge it, or acknowledge that they had ulterior motives for deprecating the content blocking APIs in favour of ones with serious limitations. For example, a performance improvement to declarativeNetRequest with an increase of the rule limit from 30,000 to something more useful, with no loss in performance.