Hi, is there any reason the hashtag symbol ("#") that prefixes tags was moved from CSS to a tag's actual HTML itself?

Hi, is there any reason the hashtag symbol ("#") that prefixes tags was moved from CSS to a tag's actual HTML itself?

The hashtag adds unnecessary noise to the tag list, making it more difficult to quickly scan a task's list of tags (since every tag starts with the same "#" character).

It seems strange to force the hashtag display by default since tags have their own default styling (which is is effective at separating from a task's content).  Also, the hashtag is not displayed when editing a task's tags (e.g. via the "tt" shortcut), resulting in an inconsistent UX between viewing and editing tags.

When the hashtag was added via CSS, I was able to hide it by using custom CSS rules.  However, now that this has been changed and the hashtag is now added directly to the CSS, users are stuck with this additional noise.

It would be great if the hashtag was once again added via CSS, or that an option be added to hide it permanently.

Thank you.

Comments

  1. Kirill Maximov (KIR)21 July 2016 at 01:33

    Hi Sol, there was a request for tags to be found via Ctrl+F in browser, and it is not possible when tags were added via CSS.

    To disable '#' in tag names, you can run in Javascript console on the Checkvist site:
    localStorage.setItem('cv.no-tag-hash', true);

    To return old behaviour, with hash tag:
    localStorage.removeItem('cv.no-tag-hash');

    Hope this suits you,

    ReplyDelete
  2. Sol M22 July 2016 at 00:02

    Hi Kirill Maximov, I set the option in Firefox's console, but it does not appear to have any effect on the tags on the page.  I've cleared the cache and hard refreshed the page, but hashtags are still prefixing tags.  Is there anything else I need to do for the option to be applied?

    Also, does this setting need to be set on each browser/device that is used to access Checkvist?  If so, then it that would mean that it cannot be applied in mobile browsers (or any other browser without console access), right?

    If this is the case, it would really be great if there were an actual option in Checkvist's settings to stop hashtags from prefixing tag names so that the UX will be consistent regardless of the browser/device used.

    Thanks.

    ReplyDelete
  3. Kirill Maximov (KIR)22 July 2016 at 01:54

    Hi, please try it out now, looks like I have not restarted the server after update.

    Regarding a separate option - could you please file a corresponding request to http://checkvist.uservoice.com?

    Thanks,

    ReplyDelete

Post a Comment

Popular posts from this blog

I'm really enjoy using checkvist, you are adding great features very quickly.

I'm really enjoy using checkvist, you are adding great features very quickly.  What I feel is missing is more use cases.  How are people using Checkvist?  What are some recommend workflows?  How many lists do you have? User Stories will not only help those of use already using Checkvist to be more effective, but attract more non-technical customers. I like to keep my lists at a minimum.  I only split out for sharing but I'd prefer not to. Here are my lists: * Inbox:  This is where zapier based integrations go.  I have Jira tickets and emails tagged with "!action" going to list which I process daily. * The List:  This is my primary list.  Everything is here.  I use sub-nodes for different areas. * Honey Do:  This is the list my wife and I share to make sure we know what we both want done around the house. * "Client Project" - I have a few Lists I share with clients (Free lance web developer). I"m looking to write a more detailed blog post. How are your l...
Read more

Hello friends

Hello friends, We are considering to change behaviour of move up/down command using ctrl+arrows for lists with hierarchy. The new approach is available on our beta site, https://beta.checkvist.com . Could you please try it out and tell us what you think? Thanks! https://beta.checkvist.com
Read more

Hello friends!

Hello friends! I'd like to ask for your opinion regarding multi-line text editing. This suggestion comes from one of our Russian-speaking customers Dolina Zamkova so here is a translated abstract of our email conversation. Current problem: When you write multi-line text, you must press 'Shift-Enter' first, then use 'Enter' to start a new line, then 'Ctrl-Enter' to submit the text. Wouldn't it be easier to have a setting that will allow using Enter to always write multi-line texts, and always submit on 'Ctrl-Enter', like you do it in text messengers? So we could add a new account-wide setting, on the Settings page: () Finish editing by pressing 'Ctrl-Enter' (convenient for multi-line text) What do you think? Do you write multi-line texts in Checkvist at all? Other thoughts of how we could make it better? :)
Read more