xxxscottyxxx I read the entire thread. And yes I saw that it has happened before you found a regression (term for a bug that keeps showing up.). Just because it keeps showing up doesnāt mean itās exactly the same every time.
Also just because values are different it can still be a threshold issue. Maybe itās a bitmask, maybe itās a URL length, may be itās a character limit, maybe itās a file size limit. Maybe Iām way off, but given my previously extensive history doing software QA thatās what my gut feel is.
Now as a PM, had this been my product I would have looked at the issue, saw it was a regression, thrown it in the backlog, and fixed it when we were in that code again unless there was a quick and easy fix that plugged the regressions form reoccurring which would likely be the least common denominator scenario, made sure the metrics showed that fix covered 80-90% of users, capped it at that and told the small minority to go pound sand. There are literally full categories on this site with less pages of videos of videos than your watch later list. At some point the list becomes unusable and the value is of the feature is diminished.
Be happy they are fixing it at all. Every bug fixed has an opportunity cost associated with it. And we all have to remember they donāt owe us an explanation, or timeline, or even a fix. This isnāt mission critical software.
When was the last time you reported a bug to Microsoft, or adobe, or salesforce, or Hulu or Netflix or apple or literally any other piece of software and got anything back beyond a thanks, weāre aware.
Iām just trying to provide you with a different perspective from behind the curtain of software development. My views obviously arenāt those of SLR and maybe thatās a good thing because they are really active in their forums and try to communicate the best they can and put up with a lot more than I would despite the constant barrage of toxic comments from its users.
