New CSS scheme?

[altenbach]

One other really serious problem here is that <shift-clicking> any thread or user profile re-uses the same browser window.

By convention, shift-clicking a link should open the link in a new browser windows, but currently this is summarily ignored. It always worked in the past! This really slows me down, because I have to reload the earlier page, which wastes a lot of time.

For example, if I am in the LabVIEW forum overview, I would like to look at a few new threads in a new window, so the overview remains as-is to quickly go back.

(Things still works if I right-click the link and "open in new window/tab", but that's significantly more tedious.)

[Hooovahh]

---

@altenbach wrote:

(Things still works if I right-click the link and "open in new window/tab", but that's significantly more tedious.)

---

The issue should be fixed, but a middle click on the mouse also opens it in a new tab.  Middle clicking the tab also closes it.

[altenbach]

My laptop does not have a middle-click....

[Hooovahh]

CTRL+Left Click seems to work too.

[altenbach]

1. Shift-left-click opens in a new window
2. Ctrl-left-click opens in a new tab AND stays on the current tab.

I prefer (1) because I immediately see the new page and can close the window if I am not interested while the original page stays right there.

In case (2), I first need to click on the new tab and then find a reliable way to go back to the original tab later.

[markwni]

Hi all,

Update at 5pm CDT / 22:00 UTC on 11-May-2022: Sorry for the silence today. We have now identified the code that is causing problems and the developers are working on it. I do not have a specific time to resolve the issues, but should be no later than tomorrow morning CDT.

Thank you,

Mark

[GerdW]

Hi Mark,

another side effect of (most probably) the same problem: when you expand any item in the forum tree (upper left widget) like "Special interest boards" the website also jumps to top.

Just to catch them all…

[markwni]

Good morning everyone,

These issues were resolved at 9:15am CDT / 1415 UTC. We apologize for the trouble and the extended time it took to resolve.

Best,

Mark

[tst]

Still seems to happen.

If I look at the Firefox developer tools at the network tab, I see a request with the following headers:

GET / undefined
Host: localhost
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0
Accept: application/font-woff2;q=1.0,application/font-woff;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Origin: https://forums.ni.com
DNT: 1
Connection: keep-alive
Sec-Fetch-Dest: font
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site

This takes 6 seconds and then 2 seconds and says that it was blocked because CORS failed.

[GerdW]

Hi,

I see similar entries in the developer tools:

Loading the website takes ~10.5s initially, with one entries failing with that "missing CORS" (chat_rules.json).

Then another ~6s later some more entries appear, so the webpage needs ~17s to load in total…

(This "measurement" is repeatable with several discussion forums here at NI.com.)

Btw. there are several HTTP status 404 entries: