Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand search on hyphenated words #7

Open
marlass opened this issue May 6, 2016 · 5 comments
Open

Expand search on hyphenated words #7

marlass opened this issue May 6, 2016 · 5 comments

Comments

@marlass
Copy link

marlass commented May 6, 2016

On properties with "-" between words you get entry not found. When you select whole property it works. It would be great if it worked with these properties only with cursor in property.

Example: place cursor in text-decoration and you get entry not found, but when you select whole text-decoration it works. Would be great if it worked with these properties like with one-word properties (eg. border).

@akamud
Copy link
Owner

akamud commented May 6, 2016

Do you mean it should work for properties like border-box if my cursor is on the border property?

@marlass
Copy link
Author

marlass commented May 10, 2016

Yep, that's what i mean.

@akamud
Copy link
Owner

akamud commented May 10, 2016

Thanks for the feedback, to tell you the truth I'm a bit concerned about cases like that, because the user might want to check for border property. HTML5 and JS properties can also have a lot of conflicts if we "expand" the search when - characters are found.

I'll evaluate this proposal and update once I study it more, thanks!

@marlass
Copy link
Author

marlass commented May 12, 2016

I think actual behaviour is confusing. You write css, have your cursor in border word of border-box property and you get that you don't need to worry about this property, because it is widely supported as CSS2.1 property and that is not true for border-box. I don't think that anyone wanted to check border property while he was in border-box property. That's my opinion about that situation.

I don't think that it will introduce a lot of conflicts with HTML5 and JS. However, when it will introduce conflicts i would suggest to turn it on at least for css, scss, less files, where HTML5 and JS properties are not so common.

Let's see what you will find out. I really like this plugin and it help me save a lot of time not needing to browse caniuse site manually. Good job.

@akamud
Copy link
Owner

akamud commented May 12, 2016

Thanks for the feedback, you do have a point about expanding this for CSS, Less and Sass files.

I'll report back as soon as I have more info.

@akamud akamud changed the title Entry not found Expand search on hyphenated words May 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants