Skip to content

BUG: date filter – DayJS stopped parsing localized dates #871

@akaleeroy

Description

@akaleeroy

Is this issue related to missing content or incorrect conversion to Markdown?

  • No. This is definitely a Web Clipper bug.

Have you reviewed the troubleshooting instructions?

Operating system

Windows 11

Browser

Vivaldi 8.0.4033.34 (Official Build) (64-bit) with Chromium 148.0.7778.183, Chromium 148.0.7778.97 (Official Build) (64-bit)

Web Clipper version

1.6.1 (latest in store) 1.6.3 (latest GitHub release)

Obsidian version

1.12.7

Describe the bug

This is a DayJS configuration bug, the | date filter can no longer parse localized dates like marți, 26 mai 2026 (Romanian)

Bug

| dateInvalid Date
| date:"YYYY-MM-DD" → unparsed string
| date:("YYYY-MM-DD", "dddd, DD MMMM YYYY") → unparsed string

Expected behavior

| date2026-05-26

URLs where the bug occurs

No response

To reproduce

  1. Go to any page with a non-English date string
  2. Try to add a date field and parse it with {{selector:h2.date-header | first | date}}
  3. See error "Invalid date for date filter: marți, 26 mai 2026" in console from popup.js:1 (Using Embedded popup mode)

There may be a clue here because the console is also showing Invalid calculation value: "/220" for {{words | calc:"/220" | round}} min.... except here it IS filling in the readtime property with a calculated value of 6 min.

Your template file

{{selector:h2.date-header | date}}

There are no syntax errors in the template.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions