Yes... I had the "firefox" set as the Custom Preferred browser and it wasn't working then I changed it to "sensible browser" and the problem was solved.
Before the broken update my Custom Preferred browser was set as "firefox" with the "open in new tab" (or something like these) enabled.
Yes... I had the "firefox" set as the Custom Preferred browser and it wasn't working then I changed it to "sensible browser" and the problem was solved.
Before the broken update my Custom Preferred browser was set as "firefox" with the "open in new tab" (or something like these) enabled.
I really think it's a transitional issue.