Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Article not marked as read on middle-clicking on "Open website" icon #2705

Open
3 tasks done
Programie opened this issue Jun 22, 2024 · 0 comments
Open
3 tasks done
Labels

Comments

@Programie
Copy link

IMPORTANT

Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)

  • I have read the CONTRIBUTING.md and followed the provided tips
  • I accept that the issue will be closed without comment if I do not check here
  • I accept that the issue will be closed without comment if I do not fill out all items in the issue template.

Explain the Problem

Nextcloud News in version 24 marked an article as read whenever I middle-clicked on the "Open website" icon (the globe icon). The latest alpha version of version 25 does not mark the article as read anymore.

Marking an article as read works fine when opening an article with a simple click on the "Open website" icon. But in that case, the browser immediately switches to the newly opened tab instead of opening it in the background.

Steps to Reproduce

  1. Middle-click on the "Open website" icon for any unread article
  2. The website opens in a new tab in the background
  3. The article is NOT marked as read
  4. Click on the "Open website" icon for any unread article
  5. The website opens in a new tab and the browser switches to it
  6. The article is marked as read

System Information

  • News app version: 25.0.0-alpha7
  • Nextcloud version: 28.0.6
  • Cron type: system cron
  • PHP version: 8.2.20
  • Database and version: MariaDB 11.3.2
  • Browser and version: Mozilla Firefox 127.0.1
  • OS and version: Ubuntu 24.04
Contents of nextcloud/data/nextcloud.log
Contents of Browser Error Console Read http://ggnome.com/wiki/Using_The_Browser_Error_Console if you are unsure what to put here
JQMIGRATE: Migrate is installed, version 3.4.1 [jquery-migrate.min.js:2:980](webpack:///nextcloud/node_modules/jquery-migrate/dist/jquery-migrate.min.js)
Unified search initialized! [UnifiedSearch.vue:51](webpack:///nextcloud/core/src/views/UnifiedSearch.vue)
AppContent pane config 35 [NcAppContent.js:2:118634](webpack:///nextcloud-news/node_modules/@nextcloud/vue/dist/Components/NcAppContent.js)
session heartbeat polling started [session-heartbeat.js:103:9](webpack:///nextcloud/core/src/session-heartbeat.js)
Contacts 
Array [ {…} ]
[UnifiedSearchModal.vue:269](webpack:///nextcloud/core/src/views/UnifiedSearchModal.vue)
Registering notifications container as a menu [NotificationsApp.vue:219](webpack:///notifications/src/NotificationsApp.vue)
Notifications permissions granted [NotificationsApp.vue:453](webpack:///notifications/src/NotificationsApp.vue)
Polling interval updated to 30000 [NotificationsApp.vue:416](webpack:///notifications/src/NotificationsApp.vue)
Started background fetcher as session_keepalive is enabled [NotificationsApp.vue:275](webpack:///notifications/src/NotificationsApp.vue)
Search providers 
Array(14) [ {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, … ]
[UnifiedSearchModal.vue:265](webpack:///nextcloud/core/src/views/UnifiedSearchModal.vue)
Got notification data, restoring default polling interval. [NotificationsApp.vue:376](webpack:///notifications/src/NotificationsApp.vue)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant