In 2 Chromium based browsers you can't make an Event through the Calendar panel on the Dashboard of the Next Cloud Webapp.

[timo-ecm2]

Issue

The Calendar app in NextCloud has a specific issue. If you try to make a new Event trough your Dashboard in Calendar panel and there are no previous Events visible in that panel, you can click on the button "Create a new event". I tested this with Chrome, Edge and FireFox. I made use of a reverse proxy.

After this a new page will load with the url "https://our-page.companyname.nl/apps/calendar/dayGridMonth/now/new/popover/0/1626163250/1626166850". The pages will continue to load, the screen stays white and nothing will happen after that.

In "the Browser console > Network" we see some things failing, of which one is a specific script. Name: nl.js? V=b1b821f1-11 and below is the header. Our language was set to Dutch and Locale also to Dutch. If you change this for both to English (US) you will see that the same things happen, but not all the time.

Below the message from the Browser console > Network.

Status: (failed)net::ERR_HTTP2_PROTOCOL_ERROR	
Type: Script
Invoke-WebRequest -Uri "https://our-page.companyname.nl/apps/theming/l10n/nl.js?v=b1b821f1-11" -Headers @{
"method"="GET"
  "authority"="our-page.companyname.nl"
  "scheme"="https"
  "path"="/apps/theming/l10n/nl.js?v=b1b821f1-11"
  "pragma"="no-cache"
  "cache-control"="no-cache"
  "sec-ch-ua"="`" Not;A Brand`";v=`"99`", `"Microsoft Edge`";v=`"91`", `"Chromium`";v=`"91`""
  "sec-ch-ua-mobile"="?0"
  "user-agent"="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36 Edg/91.0.864.67"
  "accept"="*/*"
  "sec-fetch-site"="same-origin"
  "sec-fetch-mode"="no-cors"
  "sec-fetch-dest"="script"
  "accept-encoding"="gzip, deflate, br"
  "accept-language"="en-US,en;q=0.9,nl;q=0.8,en-GB;q=0.7"
  "cookie"="oc_sessionPassphrase=IVpVC6HD6WraYvv%2B0TkvdcCCCGBNOmLNRMsjuWscNWLT093n4Epwer5YsSdnp9wu5inev%2Fl%2B1FWFemftnH86%2FK7rxRxcXdsamu59cmIs8z9ov7tnwXLz%2F%2BEaX1tAtfwx; __Host-nc_sameSiteCookielax=true; __Host-nc_sameSiteCookiestrict=true; GKimZET8LnIh=51eaa30da7dd5240caa85804a6"
}

In the browser console we see the same issue related to the one above.

Expected Behavior

Through the calendar panel in the Dashboard a user should be able to make a new Event and after clicking on the button "Create a new event". The Calendar page should open en the pop-up for adding a new event must open.

Actual Behavior

You are not able to add a new Event trough the calendar panel in the Dashboard because the Calendar page is not able not load in a Chrome our Edge. In FireFox this is not an issue.

Possible Fix

I do not know.

Steps to Reproduce

1. Login into your NextCloud environment and scroll to the Calendar panel in your Dashboard.
2. Click on the button "Create a new event" in the Calendar panel on your Dashboard.
3. The Calendar page of the app is not able to load
4. You will receive the Chromium pop-up to wait or to kill the page because it is stuck
5. In the browser console you will get the message "(failed) net:: ERR_HTTP2_PROTOCOL_ERROR".

Context

Test the environment before upgrading to 21.0.3.

Used system

Webbrowser: MS Edge Version 91.0.864.67 (Official build) (64-bit), Google Chrome Version 91.0.4472.124 (Official Build) (64-bit) and Mozilla FireFox Developer 90.0b12 (64-bit). MS Edge shows information in the web console and Google Chrome doesn't show anything yet. user account Operating system: Windows 10 Operating system: Linux Database: m=MariaDB Nextcloud version: 21.0.3 Updated from an older WebApp or a fresh install Use reverse proxy: yes

[tcitworld]

Status: (failed)net::ERR_HTTP2_PROTOCOL_ERROR

This seems like a server configuration issue unfortunately, not much we can do here. Did you try to force refresh the pages?

[ChristophWurst]

@GretaD isn't that the bug we once tried to fix? This was something about an infinite loop in js that can also crash the browser. Turning off the simple editor "solves" this loop. Did we have a ticket for this?

[tcitworld]

https://github.com/nextcloud/calendar/issues/3302 ?

[timo-ecm2]

Hi, thanks for the replies. @tcitworld yes, I did try to refresh the pages and in the browser console I disabled the cache. No positive results. @ChristophWurst & @tcitworld I will investigate #3302 more closely.

[ChristophWurst]

It was https://github.com/nextcloud/calendar/issues/2960.

[joshtrichards]

Hi @timo-ecm2 - As #3302 has been fixed, is your issue here now fixed as well from your side of things?