Skip to content

Task's start/due date timestamp gets cut off #2181

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

Open
Insprill opened this issue Jan 24, 2023 · 1 comment · May be fixed by #2833
Open

Task's start/due date timestamp gets cut off #2181

Insprill opened this issue Jan 24, 2023 · 1 comment · May be fixed by #2833

Comments

@Insprill
Copy link

Steps to reproduce

  1. Create a task with a start or due date at a specific time.
  2. Ensure your browser window is wide enough for the full date and time to show.
  3. Observe the time being cut off.

Expected behaviour

The full date should be visible if there's enough room.

Actual behaviour

The timestamp gets cut off
image

Similarly, the date switches to the short version a little prematurely when the browser window is small, due to the menu on the left being collapsed allowing for more space.
image

Server configuration

Operating system: Ubuntu 22.04

Web server: Nginx

Database: MySQL

Nextcloud version: 25.0.2

Tasks version: 0.14.5

Updated from an older Nextcloud or fresh install: Updated from 24.0.8

No errors have been found.

Nextcloud configuration:

<?php
$CONFIG = array (
  'apps_paths' =>
  array (
    0 =>
    array (
      'path' => '/snap/nextcloud/current/htdocs/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 =>
    array (
      'path' => '/var/snap/nextcloud/current/nextcloud/extra-apps',
      'url' => '/extra-apps',
      'writable' => true,
    ),
  ),
  'supportedDatabases' =>
  array (
    0 => 'mysql',
  ),
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'memcache.local' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
    'host' => '/tmp/sockets/redis.sock',
    'port' => 0,
  ),
  'log_type' => 'file',
  'logfile' => '/var/snap/nextcloud/current/logs/nextcloud.log',
  'logfilemode' => 416,
  'instanceid' => '[redacted]',
  'passwordsalt' => '[redacted]',
  'secret' => '[redacted]',
  'trusted_domains' =>
  array (
    0 => '[redacted]',
  ),
  'datadirectory' => '[redacted]',
  'dbtype' => 'mysql',
  'version' => '25.0.2.3',
  'overwrite.cli.url' => '[redacted]',
  'dbname' => '[redacted]',
  'dbhost' => 'localhost:/tmp/sockets/mysql.sock',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => '[redacted]',
  'dbpassword' => '[redacted]',
  'installed' => true,
  'maintenance' => false,
  'overwriteprotocol' => 'https',
  'default_phone_region' => 'us',
  'twofactor_enforced' => 'true',
  'twofactor_enforced_groups' =>
  array (
  ),
  'twofactor_enforced_excluded_groups' =>
  array (
  ),
  'mail_smtpmode' => 'smtp',
  'mail_sendmailmode' => 'smtp',
  'mail_from_address' => '[redacted]',
  'mail_domain' => '[redacted]',
  'mail_smtphost' => '[redacted]',
  'mail_smtpport' => '[redacted]',
  'mail_smtpauth' => 1,
  'mail_smtpname' => '[redacted]',
  'mail_smtppassword' => '[redacted]',
  'mail_smtpsecure' => 'tls',
  'loglevel' => 2,
  'mail_smtpauthtype' => 'LOGIN',
);

Are you using external storage, if yes which one: Local

Are you using encryption: yes

Are you using an external user-backend, if yes which one: No

Client configuration

Browser: Firefox Developer Edition 110.0b3, Ungoogled Chromium 109.0.5414.74

Operating system: Arch Linux

Browser log (Firefox)

Loading failed for the <script> with source “https://[redacted]/cdn-cgi/apps/head/4NQY5doIR_Bal8v53SYPBIBFYEI.js”. [tasks:15:1](https://[redacted]/index.php/apps/tasks/#/calendars/tasks)

Content Security Policy: The page’s settings blocked the loading of a resource at https://[redacted]/cdn-cgi/apps/head/4NQY5doIR_Bal8v53SYPBIBFYEI.js (“script-src”).
asavageiv added a commit to asavageiv/tasks that referenced this issue Apr 6, 2025
@asavageiv
Copy link

I think this is the offending line:

width: 60px;

The fixed widths were added way back in #992. @raimund-schluessler This was a very long time ago, but do you think the fixed widths are still required?

Alternatively, should

display: inline-block;
be changed to add width: auto on large screens to override the fixed-width from smaller screens?

@asavageiv asavageiv linked a pull request Apr 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants