Skip to main content
Carey_Smith
New Participant
April 15, 2021

Setting to turn off automated lists

  • April 15, 2021
  • 54 replies
  • 19480 views

Does anyone know how to turn off Figma’s auto-formatting? I’m trying to type '- ', but it looks like Figma is assuming this text must be a bulleted list.

I’m having a similar issue when using text that’s in the format of an email address or a url. Figma is changing these to unwanted links. I’d like to turn off all text auto-formatting.

54 replies

Shawn1
August 13, 2021

I have a numbered list that continues on the other side of an icon so it will need a separate text box. Please allow list editing capabilities

  1. input any start number
  2. adjust the amount of indent

OR

  1. allow indentation from line to line in a paragraph through use of space/tab to “fake” a numbered list as you can in word processing software.
Shawn1
August 13, 2021

Hi - I have a work around for list items in separate boxes

Make one list.
Create a frame.
Copy and past framed list and adjust to fit the next menu item.
Not optimal but it does work for my purpose.

Would be nice not to have to go through the formatting headaches though.

Please consider updating this feature!

Thanks

Figma_Bot
August 16, 2021

So annoying, It should turn off by default.

August 20, 2021

seems like figma got so excited about the fact that they could, that they forgot to ask if they should.

this should be a user configurable setting.

i would think this should be off by default as has been said. at no time have i benefited from this feature and now it is actively impeding my work. granted i can work-around it by creating two distinct text boxes that appear as one, but i should not have to.

i also think this setting should be file specific, as it seems very likely that in one file a designer might want this (not me personally, but there must be people that like it), but in another file this might be unwanted behavior.

until the automatic lists can be styled to suit the project, i do not ever see this feature being of any value. figma is not a word-processor and the automatic list feature in ms word is problematic. i have seen myself and others fight with it so often to get it to do what we want it to, that it takes more time than just manually indenting and numbering or bulleting. and microsoft has been working on that for decades. that is why i use indesign or sublime text for any word-processing i need to do.

the auto list feature was an ill-conceived, poorly implemented waste of effort. should have spent the time on branching, auto-layout fragility, nested component controls, or any other of the so many feature requests on this forum.

Gleb
Power Member
September 3, 2021

I totally agree, pressing Cmd/Ctrl + Z after every list item when you don’t need a list is super annoying. I want to disable this feature!

Dima_Zhukov
September 14, 2021

For example:

  1. Item Name
    Item description

  2. Item Name
    Item description

  3. Item Name
    Item description

The first item will be formatted differently and fixing it causes extra work, please add an option to turn numbered formatting for any number, not just 1, or the option to disable auto-formatting.

It could be a cool feature, but currently, in most cases, it is just annoying!

ose.design
December 15, 2021

If you:

  1. Type the numeral ‘1’.
  2. Then hit space and type a full stop/period.
  3. Then return the cursor to before the ‘.’.
  4. You can hit backspace to format things correctly.
  5. And then the indent is not applied.

And no, there was no need to use a numbered list to explain this.

MitchR
February 12, 2022

@ose.design Cool solution. Thanks.

Christina9
February 24, 2022

Appreciate you sharing a workaround. To be honest, this only further demonstrates the needless and annoying things that Figma users need to do to compensate for the absence of a very basic functionality.

Not trying to rip on Figma because I am a huge fan. But I feel features such as this are no brainers and really shouldn’t take so long to implement.

Gleb
Power Member
February 24, 2022

I think this workaround is simpler: