...
Status | Feedback | Suggestion | Commenter | Response | ||||||
---|---|---|---|---|---|---|---|---|---|---|
| Slider issue - we are using a slider on AQM UI and we noticed that the slider designs in Figma LUX library and in Zeplin aren’t the same. | Hi Ori Cohen, the correct slider variants have been added to the component set now - feel free to have a look 😊. In response to the slider without ‘ticks' request, a nice temporary solution could be to toggle these off in the layers tab to hide them on the canvas. | ||||||||
| Add OOTB interactive capabilities to the components e.g. hover state changes for buttons and click actions for toggles, checkboxes etc | Has been added to the component library | ||||||||
| Text in dropdown should be auto width | Hi Asaf Ben-Oved, this should now be resolved, if you’d like to take a look. | ||||||||
| Checkbox & Radio Button | add the option to add text to a checkbox within the component. | Hi Omer.Glazer (Unlicensed), the option to add text should be available for both checkboxes and radio buttons now. | |||||||
| Dropdown | Removing menu items doesn’t auto resize the menu containers height | Femi, as discussed, this issue should now be resolved and published. | |||||||
| Text link - see image | Asaf Ben-Oved, as discussed, this should now be resolved and published. | ||||||||
| I tried to make a color change to the icon, but I saw this, maybe its OK and maybe not. | Make a simpler hierarchy? | Asaf Ben-Oved , not sure why it happend to you, but all the icons in the library have only a component wrapper, make sure its an icon from the library and not one of yours Asaf: Yes this is my bad - Thanks | |||||||
| States are not declared correctly? | Asaf Ben-Oved, I noticed the name of the component in use in your screenshot was ‘Drop-down Menu’, shown in the properties pane on the right. This must be an old component/version of the dropdown menu. The most up-to-date component is called ‘Dropdown Menu', as shown below. Perhaps a sync on your end will pull this through? | ||||||||
| Should tabs dynamically resize based on the tab’s text label? Also, responsive tab design in current documentation is different to Zeplin designs. | First level tabs extend to the entire containing container 2nd level are sized per tab | ||||||||
| Tryng to shorten the width of a list doesn’t change the rows | Make rows resized according to main frame | Asaf Ben-Oved this is fixed now | |||||||
| Changing the text in the list also change the text I already input | Changing states should not overwrite the text | Yehiel Elad-Certner (Unlicensed) looking at fix | |||||||
| No asset for dialog and wizard | Add these assets | Yehiel Elad-Certner (Unlicensed) working on it | |||||||
| The stroke for the text field and for the dropdown is of a different color | Change so they have the same color | Yehiel Elad-Certner (Unlicensed) working on it | |||||||
| Cant find a recycle bin icon | Add | Ayelet Servi Icon is called ‘Trash’ in the library | |||||||
| Toggle (switch) - Looks to me a bit too large (compared to the radio button for example like you can see in the image here). Is it me or do you also think we should make it smaller? | Ayelet Servi That is correct, the currently implemented toggle is the default base toggle size - https://app.zeplin.io/project/5970b366bee38cf87b2de932/screen/60215bfbe9271d153359f985 I’ll add the small toggle variant (https://app.zeplin.io/project/5970b366bee38cf87b2de932/screen/60f7c70930286e161ee453dd ) to the schedule. | ||||||||
| The Speaker icon - I think that we should consider changing its name in the asset to Audio (Since that’s what it represents in our products) | Change icon’s name | Ayelet Servi The icon is already in use in various applications under that name hence Guy doesn’t think it would be worth renaming as it will create technical issues. Femi OK, thanks | |||||||
| The gap between a radio button and a label should be 6px? at least from what I saw in Zeplin. This is it looks currently | Change the gap from 10px to 6px. | Hi Asaf Ben-Oved, this has been updated 👍 | |||||||
| See feedback within the movie
|
| Hi Asaf Ben-Oved, tooltips have been updated to allow users to manually adjust the width. Removing the gap between the tooltip component and purple selection box was not possible in variants that show the top arrows, since these elements use absolute positioning (which allows us to achieve the visual design where the pointed arrow cuts into the tooltip’s stroke). Where possible, the relevant variants have also been updated so there is no gap between the tooltip and the selection box. | |||||||
| In the assets - can’t find a toast message (although it appears as “done”) | Add the toast. Thanks | Ayelet Servi It should now be published and available | |||||||
| The current watermark is only set to be used on top-right corner. There are times when we need it on a different corner since that corner has some functionality that need demonstration. | Make the watermark adjustable for all 4 corners of the screen | Done. | |||||||
| Different disabled styling between a dialog button and a split button | Align the styles | Asaf Ben-Oved done. | |||||||
| I’m missing an orange warning icon (I see only a gray one). Need it for inline messages. | Add to the assets | Ayelet Servi All icons come in the default grey out of the box. Once on the canvas you can change the icons color in the ‘Selection colors’ section of Figma’s design tab Femi That’s what I did, but since each type has one appropriate color only, isn’t it better that we have the colored ones already ready in our assets? Also, do you know when we are supposed to use the gray ones and when the colored? Ayelet Servi The icons themselves are all created as vector icons in exactly the same format so that they can be resized and recolored by the designer depending on their desired purpose (as the same icon may be used or colored in different ways). When we have components that make use of a specific icon asset (e.g. Tooltips, icon buttons etc), the icon is styled accordingly within the component itself. Femi OK, thanks Femi | |||||||
| This icon is called “Folders” in the assets | Should be called “Open folder” | Hi Ayelet Servi, this icon is already in use under the same name in various applications, so we don’t think it would be worth renaming it due to the technical issues it would cause. | |||||||
| Icon buttons with a label - the frame doesn’t adjust to the label text | Auto-adjust the frame to fit the label. Otherwise it causes a problem in auto-layout. (But not a big problem to fix manually). | Hi Carlie Bradshaw, this has been fixed. | |||||||
| Popup has fixed width buttons | Have to detach for buttons which aren’t short single words. (Lots of examples in the common messages repository, e.g. keep editing/leave anyway). | Hi Carlie Bradshaw, these buttons have been updated to hug contents 😊 | |||||||
| Missing canvas section. This is needed in order to organize the canvas space. Also these sections should have a big enough font to be able to see while you are zoomed out | see example | Ori Cohen Done. | |||||||
| Removing icon from a tree list item doesn’t align label to the left, as it does in a normal list | Hi Carlie Bradshaw, this seems to be working now, would you mind checking again to see if it is on your end as well? Hey Femi , it’s these ones which are causing the problem: Hi Carlie Bradshaw, the tree component has been updated and published - these issues should be fixed now 😊. | ||||||||
| Date picker menu should start from Sunday and not Monday | Set the date picker menu to start from Sunday | Hi Asaf Ben-Oved, this seems to have already been updated so the week starts from Sunday. For other calendars (with weeks that start on Monday), is it reasonable to expect designers to update this manually? | |||||||
| Hover state of a cell in the date picker menu is incorrect | From the LUX wiki page. Hover is used as a stroke not a font color | Hi Asaf Ben-Oved, this has been updated with the correct visual design. | |||||||
| Resizing the Canvas title doesn’t adapt the background color | Allow the background to also resize | Was fixed by Ori Cohen | |||||||
| In tooltip the “Plain text” and “Header” should be under the Type menu and not the State menu | Put header and Plain text under the Type menu | Hi Asaf Ben-Oved, the tooltip properties have been updated 😊 | |||||||
| Inconsistency in changing menu width when done from action menu - width changes by text in dropdown - width changes by manually change | change the width both “hugging” and by manual pull | Hi Asaf Ben-Oved, it was Guy’s request to have all menus that are connected to input fields to be the same width as the field, hence the manual resize for the dropdown menu component. Since we would want the icon above the action menu to be a fixed width, we allow users to dictate the width of the dropdown menu here with the list item label instead. So, although these behaviours are different they are both intentional and considered appropriate for the reasons above. | |||||||
| A time picker in a disabled state still has the icon in it shows as in regular state | The design is | Hi Asaf Ben-Oved, the icon has been updated. | |||||||
| Missing “Clear” icon for the search field (or the search field state that includes this icon). | Add | Hi Ayelet Servi, the ‘clear’ icon should be visible in the search field when the ‘filled’ type is selected. | |||||||
| There’s a bug with the dropdown list: Before run - The texts of the options appear as they shoud: When running - The texts sometimes (might be related to making it active) go back to their default: | Hi Ayelet Servi, we ran a lot of tests to try to fix this but unfortunately had no luck - we believe it’s a bug in Figma’s presentation mode. Sometimes refreshing the prototype seems to resolve this issue, but other times the text does reset to it’s default label. | ||||||||
| Missing a state in toast where its a warning and also has the expand/collapse | Hi Asaf Ben-Oved, these variants have been added 👍 | ||||||||
| Cannot put a storke on bottom part of of the list - see image | Allow full stroke for a list | Hi Asaf Ben-Oved, this should be fixed now. | |||||||
| Selected state in Menu seems not to be working | Fix according to state | Ori Cohen Fixed (31.10.22) | |||||||
| Icon buttons remaining in hover state when we mouse off. | Ori Cohen Works fine | ||||||||
| In prototype mode, a clicking on a dropdown opens the menu but it disturbs the pop-up. I’m not sure where is the problem, but these are both Figma components which I didn’t apply any interaction on see recording | Either remove the click-to-open a menu or check to see what is the cause of problem. | Ori Cohen Fixed (31.10.22) | |||||||
| The wizard dialog includes OK and Cancel buttons | Will include the Next and Back buttons | Ori Cohen Fixed (31.10.22) | |||||||
| Slider doesn’t have a disabled state | Add | Ori Cohen Fixed (31.10.22) | |||||||
| Slider state dropdown mixes states like disabled, enabled, focused with the full/half/empty states | Separate the two so we can have, for example, a full disabled slider | Hi Ayelet Servi, these variants have been added 😊 | |||||||
| Wizard stages - I can’t find an easy way to change the status of the circles (Completed, current, future. not sure if these are the best names) | Add a status dropdown like in other components | Solved. (08.11.22) | |||||||
| Selectors are fine when the first node is the one selected. However, switching the second one to Selected and the first to Regular results in missing borders | Result: | Hi Carlie Bradshaw, this has been resolved and updated. | |||||||
| Drop down component (single selection) stays open after we select a value or click outside. (Example swapping between 2 modals) | The dropdown will automatically close after we select a value. | Hi Carlie Bradshaw, here’s the example I was referring to in the comment thread: | |||||||
| Please add the empty state to Search with AutoSuggest | HiAsaf Ben-Oved, done! | ||||||||
| Missing the Searchable Multi-select drop down option . currently it only supports Searchable Single-select | Please add this | Hi Asaf Ben-Oved, the multi-select dropdown and searchable multi-select dropdown variants have been added 👍 | |||||||
| Fillable text fields/areas | I have no idea if this is even possible in figma, but it’d be real nice if the user could actually enter text into text fields in prototypes? | Carlie Bradshaw Unfortunately not yet but the feature request has a fair amount of votes on their forum - https://forum.figma.com/t/interactive-text-inputs-in-prototype-mode/366/29 | |||||||
| Annotation position order | please set the order as
So it makes some mapping between the text position in the menu and where the text bubble will appear | Hi Asaf Ben-Oved Now fixed! | |||||||
| Mouse cursor icons. In the Sketch library there was a set of mouse cursors that was built for the UX (as I remember). I don’t see these icons now. For example, when dragging an object the mouse cursor change to a gripping hand | Move the set of mouse cursors from Sketch to the Figma library | Asaf Ben-Oved Done. | |||||||
| The background of the popover is transparent. | Change to opaque (as default). | Ayelet Servi Done 👍 | |||||||
| For the “popup” asset - the combination of Dialog-General-Large is not allowed | Allow | Ayelet Servi Added 😊 | |||||||
| Dual list selector - the name “Selected columns” is different from the name in the documentation (“Chosen columns”) | As far as I understand the name should be changed to “Chosen columns”, so as not to confuse with the selection done with the checkboxes. | Hi Ayelet Servi, this has been updated 😊 | |||||||
| Please fix title position. see screen video | Asaf Ben-Oved Fixed! | ||||||||
| The wizard asset - When we stretch it the padding between the buttons and the right side of the dialog gets larger and larger (relatively to the dialog’s size). | I think that the padding should stay fixed. | Ayelet Servi Fixed! | |||||||
| Allow pop-over to put the arrow in all directions and. not just to the left | Ethan McGonigle (Unlicensed) Will reuse the same technique applied in annotations. | ||||||||
| Time Picker icon name incorrect | Labelled ‘Regular/ime Picker copy’. Missing T makes it hard to find, and not sure why it’s a copy. | Carlie Bradshaw Should be fixed now | |||||||
| List with two rows uses the wrong styling see picture |
| Hi Asaf Ben-Oved, these issues have been fixed - should all work/look as intended now. | |||||||
| Tree asset - For some reason when I moved branches to be third level they changed their background to white: | Same transparent background as the rest | Ayelet Servi We’ve tested and couldn’t replicate the bug. Can you verify and let us know please? Femi Ethan McGonigle (Unlicensed) - I can’t replicate it either now. Please ignore and if it happens again I’ll report. | |||||||
| Icon button - For some reason, after I replace the original icon with the icon I want, the option to change it’s properties disappears. | Fix please. | Ayelet Servi We’ve tested and couldn’t replicate the bug. Can you verify and let us know please? NOTE: You have to be on the correct instance in your layers for the properties to show up. Femi Ethan McGonigle (Unlicensed) - I’ll be happy to show you. Hi Ayelet Servi, we’ve added the ability to swap icons in the component properties now as well, so no need to do this via the layers anymore 😊. | |||||||
| I miss 2 states in the date picker:
| Hi Liat Vax, added 😊. | ||||||||
| Small switch/toggle button with text isn’t aligned correctly in files. | It’s odd. It looks fine in the LUX figma file, but copying or adding to another file causes the text to be misaligned. Demos of problem: | Hi Carlie Bradshaw, thanks for the demos! Fixed 😊 | |||||||
| Dropdowns don’t have read only state | Hi Liat Vax, this is intentional 😊, the relevant dropdown menu states can be seen here - https://kanasoftware.jira.com/wiki/spaces/UserExp/pages/659358568/Drop-down+Menu#States. | ||||||||
| ‘Tag’ icon doesn’t resize | Container size changes but actual vector doesn’t. NB: ‘Tags’ icon (plural) resizes fine. | Hi Carlie Bradshaw, fixed. | |||||||
| Errant line in Copy icon | The left-hand line shouldn’t extend to the bottom (according to the LUX iconography page). | Hi Carlie Bradshaw, I noticed this as well! Thanks for the iconography page reference to verify the correct vector. Fixed. | |||||||
| The tree component does not let us add lines to it | Add hidden lines | Fixed. | |||||||
| Add an instance to the pop over component so the content can be swapped | Add an instance | Asaf Ben-Oved give it a try. | |||||||
| Toggle / switch text alignment is broken on small size | Needs to be fixed | ||||||||
| Toggle - vertical text alignment | Solve the alignment | Shiri Klein Somberg (on behalf of Guy Hivroni (Unlicensed)) | Shiri Klein Somberg , Guy Hivroni (Unlicensed) Fixed and fixed :) | ||||||
| Radio buttons internal dot not the same size as in zeplin | Align with Zeplin design | Ori Cohen 25.6.23 | |||||||
| Bug in confirmation messages with the buttons. When hovering over the buttons this happens: | Ori Cohen Fixed | ||||||||
| Tooltip, | should be modified as 28 px height and find the right frame paddings. | ||||||||
| Can’t add more than 5 primary tabs | Can’t add any more than the given 5 without detaching. (Don’t think there’s any LUX guidance saying you can’t have >5) | Fixed (19.09.23) Added 5 more | |||||||
| Dropdown changes text content when we change its state. | The text will not change. | Fixed (19.09.23) Ayelet Servi | |||||||
| When adding a text field and switching to Read Only, the text color is #666 instead of #333 (see Zeplin). | Update the Filled, Read Only state text to #333. | Assigned to Hasitha Jayarathne In Zepling Read Only text color is not #333 it’s #666. | |||||||
| Add read-only checkbox | Add read-only checkbox | Is that the correct design? | |||||||
| Text color in readonly (textfields etc) not black enough according to Guy Add 'readonly states for drop down (even though not supported in html) | Check Zeplin | I’m trying to understand how we want to approach the first part. | |||||||
| Update components read-only font color and add read-only states to components missing them | Make sure all Figma library elements use the right read-only colors | Shiri Klein Somberg (on behalf of Guy Hivroni (Unlicensed) and Asaf Ben-Oved) | Itay lapid (Unlicensed) looking into this | ||||||
| Probably need to have menu ‘group headers’ added as a component. Documented in the following places: | Could possibly be added the same way as menu dividers within the ‘1. Option Item’ object… Figma example can be found in the following file ('Other Examples') page: | Femi I remember Ethan and I worked on this one. Ori Cohen Sorry this one was actually already done. I just forgot to mark it as done here and move it to completed |