Assigned

Bug

Status Update

No update yet.

Description

ch...@google.com

created issue on behalf of wb...@gmail.com #1

Mar 3, 2025 01:04PM

Steps to reproduce the problem

Develop an SPA application and use the 'a' tag to perform routing jumps within the system
Add the visited attribute to tag a and change the color after accessing it
When clicking on tag a, the page remains unchanged
Refresh the page using the reload API, and then click on the 'a' tag to change color

Problem Description

I added the 'visited' pseudo class to the 'a' tag in the code, but after upgrading to the latest version 133, elements with the 'visited' pseudo class did not change color when clicked.
When I re render the page using reload and click on the element again, the color changes as expected

Additional Comments

无

Summary

The visited attribute of cssd is invalid in use

Custom Questions

Which component does this fall under?

Blink>CSS

Does this work in other browsers?

Yes - This is just a Chrome problem

Additional Data

Category: API
Chrome Channel: Stable
Regression: Yes

Comments

dt...@chromium.org <dt...@chromium.org> #2Mar 3, 2025 04:52PM

This could be the impact of this change:

https://chromestatus.com/feature/5101991698628608. Have you tried disabling it and seeing if it works with the feature off?

wb...@gmail.com <wb...@gmail.com> #3Mar 4, 2025 02:38AM

how to disabling it

pe...@google.com <pe...@google.com> #4Mar 4, 2025 02:42AM

Thank you for providing more feedback. Adding the requester to the CC list.

dt...@chromium.org <dt...@chromium.org> #5Mar 4, 2025 06:24PM

chrome://flags/#partition-visited-link-database

ka...@google.com <ka...@google.com> #6Mar 5, 2025 12:23PM

Reporter@:- Could you please tr to disable the flag as mentioned in

comment#5

and let us know the if it works with the feature off?

Thanks..!!

wb...@gmail.com <wb...@gmail.com> #7Mar 5, 2025 12:39PM

Because I have used reload on my end, it cannot be reproduced at the moment

pe...@google.com <pe...@google.com> #8Mar 5, 2025 12:43PM

Thank you for providing more feedback. Adding the requester to the CC list.

ka...@google.com <ka...@google.com> #9Mar 6, 2025 01:25PM

@Reporter: As per your

comment#7

the issue seems to be resolved.Can you please confirm if this issue can be closed?

Thanks

mi...@google.com <mi...@google.com> Mar 12, 2025 01:15PM

Assigned to mi...@google.com.

ky...@google.com <ky...@google.com> Mar 12, 2025 01:16PM

Reassigned to ky...@google.com.

mi...@google.com <mi...@google.com> #10Mar 12, 2025 01:18PM

Thanks for the report @wb94120.

Can you clarify the following:

Develop an SPA application and use the 'a' tag to perform routing jumps within the system

Are you using any framework in particular? Does clicking on "a" do a real navigation, or is this using pushState and re-rendering the page content?

Add the visited attribute to tag a and change the color after accessing it

What do you mean by adding the visited attribute? Are you doing something manually, or relying on the browser to mark the link as visited?

ka...@google.com <ka...@google.com> #11Mar 14, 2025 05:43AM

Reporter@ could you please provide your inpust as per

comment#10

As the issue is in assigned state removing unconfirmed and also Needs-Bisect hotlists. Please feel free to add it back if required

Thanks..!!

pe...@google.com <pe...@google.com> #12Mar 14, 2025 03:35PM

The NextAction date has arrived: 2025-03-14 To opt-out from this automation rule, please add Optout-Blintz-Nextaction-Alert to the "Chromium Labels" custom field.

IssueTracker

This issue is a part of the Chromium tracker.

The visited attribute of cssd is invalid in use

Status Update

Description

Steps to reproduce the problem

Problem Description

Additional Comments

Summary

Custom Questions

Which component does this fall under?

Does this work in other browsers?

Additional Data

Comments

dt...@chromium.org <dt...@chromium.org> #2Mar 3, 2025 04:52PM

wb...@gmail.com <wb...@gmail.com> #3Mar 4, 2025 02:38AM

pe...@google.com <pe...@google.com> #4Mar 4, 2025 02:42AM

dt...@chromium.org <dt...@chromium.org> #5Mar 4, 2025 06:24PM

ka...@google.com <ka...@google.com> #6Mar 5, 2025 12:23PM

wb...@gmail.com <wb...@gmail.com> #7Mar 5, 2025 12:39PM

pe...@google.com <pe...@google.com> #8Mar 5, 2025 12:43PM

ka...@google.com <ka...@google.com> #9Mar 6, 2025 01:25PM

mi...@google.com <mi...@google.com> Mar 12, 2025 01:15PM

ky...@google.com <ky...@google.com> Mar 12, 2025 01:16PM

mi...@google.com <mi...@google.com> #10Mar 12, 2025 01:18PM

ka...@google.com <ka...@google.com> #11Mar 14, 2025 05:43AM

pe...@google.com <pe...@google.com> #12Mar 14, 2025 03:35PM

Issue 400254620

Description

Steps to reproduce the problem

Problem Description

Additional Comments

Summary

Custom Questions

Which component does this fall under?

Does this work in other browsers?

Additional Data

Issue summary

Comments

dt...@chromium.org <dt...@chromium.org> #2Mar 3, 2025 04:52PM

wb...@gmail.com <wb...@gmail.com> #3Mar 4, 2025 02:38AM

pe...@google.com <pe...@google.com> #4Mar 4, 2025 02:42AM

dt...@chromium.org <dt...@chromium.org> #5Mar 4, 2025 06:24PM

ka...@google.com <ka...@google.com> #6Mar 5, 2025 12:23PM

wb...@gmail.com <wb...@gmail.com> #7Mar 5, 2025 12:39PM

pe...@google.com <pe...@google.com> #8Mar 5, 2025 12:43PM

ka...@google.com <ka...@google.com> #9Mar 6, 2025 01:25PM

mi...@google.com <mi...@google.com> Mar 12, 2025 01:15PM

ky...@google.com <ky...@google.com> Mar 12, 2025 01:16PM

mi...@google.com <mi...@google.com> #10Mar 12, 2025 01:18PM

ka...@google.com <ka...@google.com> #11Mar 14, 2025 05:43AM

pe...@google.com <pe...@google.com> #12Mar 14, 2025 03:35PM

Add comment

Issue metadata