Bitbucket just got broken for PM! Topic is solved

[dinosaur]

Another Javascript issue is creeping up, and this time in bitbucket:

bitbucket.png

Firefox works fine (tested with v84.0.2).

[vannilla]

It's a known issue and there's a bounty on it.
For those not knowing about the bounty program, it means the task is difficult to some extent and the developers are offering money to anyone successfully tackling it.

[Pentium4User]

Off-topic:
How is this window theme called?

[EMH_Mark_I]

Off-topic:
How is this window theme called?

Off-topic:
Crux. It use to be available in the xfwm4-themes package on Debian Stretch, but I haven't seen that package in awhile now. You can still download it from the package archive. You'll have to extract the contents from the deb file.

[dinosaur]

It's a known issue.

Nope, this is a new issue: it happened an hour or so before I posted this report Before that I could browse commits on github (doing it daily, as a developer) and only a few (totally dispensable) features were not working. Now, all I get is a blank page and I have no other choice than using another (lesser) browser to work with github...

PS: as for the the theme, yes, it's Crux (GTK2 theme only, alas). Using Sawfish as the window manager and a patched version of MATE v1.14 (last GTK2 compatible version). I hate the ugly flat themes imposed nowadays, and GTK3.

[dinosaur]

It seems this issue got acknowledged by bitbucket (it also affects other browsers, including older Firefox versions). See this message.

[dinosaur]

Posted a support ticket (with same screen shot). Got a reply from bitbucket and issue is now fixed after I suggested they simply revert the culprit script...

[Moonchild]

Nope, this is a new issue

Nope it's a known web compatibility issue in UXP in general. We have an open issue in our tracker for it. (optional chaining)
Solution for this is simple on the web server side, simply don't try to shorthand everything and do a check for the object before checking the sub property.
So :
e?.account_id should be a check for (e && e.account_id) to check if e isn't null or undefined first before trying to access the account_id property.

[New Tobin Paradigm]

Their wording and the fact they didn't think to simply revert the code just proves everything we been saying for years. Not only are they doing this shit without thinking they also aren't testing anything properly.

[dinosaur]

Their wording and the fact they didn't think to simply revert the code just proves everything we been saying for years. Not only are they doing this shit without thinking they also aren't testing anything properly.

+1

At least, they reacted quickly and appropriately, and they just apologized:

Dheeraj commented:

Thanks for your reply.

Initially, it seemed like the issue was related to the browser version as some users(especially Firefox users) confirmed that it worked fine after updating their browser to the latest version.

But you are right, the issue was due to a script. Our development team has rolled back the script changes and fixed the issue now.

Kindly verify if it is working fine on your end.

If you experience any further issues please let us know by responding to this ticket.

We apologize for the inconvenience caused due to this issue.

Best Regards,
Dheeraj B
Bitbucket Cloud Support