@Rosalie_WMDE i used ­F37030053 to show the hover behavior, since for some reason the other examples on the menu page don't work for me. That is the behavior I was replicating in the mocks, so to me it does match whereas the implemented menu looks more like buttons in a menu to me. It's in this section on the vuetify page. Can you tell me if the other examples show a different hover behavior to you? Maybe it makes sense to have a call to make sure we're looking at the same thing.

Hey @Rosalie_WMDE thank you for the ping and your work so far.

We've agreed now to change the font size to 16px starting at the breakpoint of 640px width and smaller viewports. I have added some specs in the respective figma file. Lemme know if there are any open questions!

hm, then i have no idea what's going on. Maybe @Evelien_WMDE can check her version number?

no, that, looks correct. are you using the chrome app? @Deniz_WMDE

Point 2 remains. Seems to be an Iphone things since this problem does not appear when using android

@Evelien_WMDE none of the two first points appear when i test it, so i'm not sure where the problem lies.

had a chat with dat and everything looks great!

@dang Favicon looks good.

uff, good catch, thanks evelien! will make a separate ticket for this!

Sorry for the late response! Looks great now @dang :)

Hey everyone,

@dang @Tarrow i've added the snackbar error state in the figma file. Let me know if you have any questions!

Thanks for sharing @Rosalie_WMDE ! Here are my remarks:

Addition regarding the message field:

@whoever picks this up: please give me a ping when you do so, I would love to do the snackbar part together. thanks!

In T305819#8236018, @GreenReaper wrote:

As a user, I think it makes sense to turn it disabled while it is being submitted, so that I don't accidentally double-submit the form by double-clicking or input bounce. I don't know if doing so would result in a second email and if that would invalidate the first email sent, but if so that would be bad because if the user then opened the first email, the reset would then "not work". It also indicates to the user that the input has been accepted by the browser.

However once the message has been sent (or not sent, in the event of a failure) and the rest of the UI updated, it would make sense for it to be enabled again, either because you have multiple accounts to reset or, as Charlie says, you might have the email wrong the first time.

In T305819#8236182, @dang wrote:

One more thing I found out. When I hit Enter instead of Reset Password, it didn't work and I received no email.

Overall looks really good to me!

I'm assuming it's vuetify and will proceed under that assumption until someone tells me otherwise

In T299498#7717454, @Tarrow wrote:

Finally there is one tiny open question about the tile setting for the v-card aimed at @Charlie_WMDE. To quote from something I asked in realtime chat:

I was reviewing the FeddyProps change and I was surprised to see in the code that we tweaked the card to add a tile setting to the v-card
I then looked in the figma sketch and saw that it also had a tile explicitly mentioned in the descriptive box
but to me the picture looks like tile is not set. As I understand it tile mode results in sharp rather than rounded radius corners on the card

@Samantha_Alipio_WMDE I added the taget speeds to the table. would like to discuss the two parameters with an asterisk on Monday to see how to proceed

After talking with Lydia, we decided that as a first step we will remove the gif part of the popover and leave the descriptive text as a sort of extended tooltip to try to marry the interests of both user groups. Let's see if that is perceived as less intrusive, and if not, we can continue talking about other alternatives.

Hey Sarai, thank you for your suggestions. I think they're great and we should implement those changes to the components if that still makes sense in your opinion.

Hey @Abbe98, thanks for creating this ticket. Your point makes a lot of sense and I've been thinking on how to improve the situation.

Hey @Lydia_Pintscher since this is not part of any project that UX has allocated resources for, this will probably not be picked up by us. That being said I'd be happy to find a working mode for these types of "maintenance" tickets and how to handle them in the future. I will raise all these points in the next team meeting and get back to you. My assumption is that this will require a little bit of PM<>UX communication to find a good working mode.

yay, looks awesome \o/ @Lydia_Pintscher good to go from my side

Hey @Botoxparty I just had a look at the link.

looks good. i'm just not sure why the column headers are displayed in such a large font (at least in firefox)

behavior seems fine. the lack of border on focus and not being read by the screen reader should be fixed.

works!

cool, looks good then!

@bete it's great but now the improvement from earlier T274273 was undone. could you take a look? Or was that change worked on a branch that doesn't include the other improvement yet?

awesome! \o/ leaving open so product to have a look too

yay, works for me! but would love for someone else to double check with some more examples. (i checked the example above and instance of cathedral located (P131) in france).