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

[BUG] View widget's template attribute is broken #8611

Open
Leilei332 opened this issue Sep 17, 2024 · 7 comments
Open

[BUG] View widget's template attribute is broken #8611

Leilei332 opened this issue Sep 17, 2024 · 7 comments

Comments

@Leilei332
Copy link
Contributor

Leilei332 commented Sep 17, 2024

Describe the bug

The view widget's template attribute is not working, which cause the date to fall back to default format. I think it may be related to 6ae00e4.

Screenshot_20240917-132603

Expected behavior

No response

To Reproduce

No response

Screenshots

No response

TiddlyWiki Configuration

5.3.6-prerelease

Additional context

No response

@pmario
Copy link
Member

pmario commented Sep 18, 2024

@Leilei332 -- Please also post the code as plain/text, so it's easier to verify the issue.

@pmario
Copy link
Member

pmario commented Sep 18, 2024

It works fine for me:

Edit: I probably clicked the wrong tab - sorry. See: #8611 (comment)

@pmario
Copy link
Member

pmario commented Sep 18, 2024

That's funny. I did try it with Edge and it fails:

grafik

@pmario
Copy link
Member

pmario commented Sep 18, 2024

It seems the TW prerelease with Edge fails and tw-com works as expected. I'll try to disable codemirror plugin in prerelease to see what happens.

Edit: No luck - Edge - empty-prerelease.html also has the problem

@Leilei332
Copy link
Contributor Author

It didn't work on firefox (ESR 115.15.0) and chrome (128) on my computer, using the empty edition.

Plain text:

<$view field="modified" format="date" template="DDth MMM YYYY at hh12:0mmam"/>

图片

图片

@pmario
Copy link
Member

pmario commented Sep 18, 2024

uups -- You are right. I does not work for me with FF either. May be I did click the wrong tab, so I was confused. Sorry.

I did find the problem already. -- It's a prerelease problem

@kookma
Copy link
Contributor

kookma commented Sep 18, 2024

I can confirm this bug on Edge 128/Win 11
TW 5.3.6pre.

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

No branches or pull requests

3 participants