Bug 325492 - css.xml: Doesn't understand CSS3 keyframes queries
Summary: css.xml: Doesn't understand CSS3 keyframes queries
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: syntax (other bugs)
Version First Reported In: 3.11.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Joseph Wenninger
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-10-01 10:20 UTC by Kai Uwe Broulik
Modified: 2018-10-27 03:32 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2013-10-01 10:20:20 UTC 
Kate's CSS syntax highlighter doesn't understand CSS3 keyframe queries.

Enter for example
> @keyfrmes some_nifty_animation {
>  0%   { opacity: 0; }
>  100% { opacity: 1; }
> }

and it will erroneously underline red the 0% { part, no matter what you place there (5px, foo, nothing), it just doesn't like brackets inside brackets.


Reproducible: Always
Comment 1 Jan Keith Darunday 2014-02-08 18:29:27 UTC 
I'm experiencing this too.
from and to is being highlighted wrongly too as what happens in the following example:
@keyframes someAnimation{
    from { opacity:0.0; }
    to { opacity:1.0; }
}
Comment 2 Dominik Haumann 2015-10-08 07:32:46 UTC 
Could you look into css.xml and maybe provide a patch?
Comment 3 Christoph Cullmann 2016-01-31 16:45:09 UTC 
If you still want that, please take a look at 

https://docs.kde.org/stable5/en/applications/katepart/highlight.html

If you provide some file as patch on https://git.reviewboard.kde.org/ we can
have that, otherwise this won't happen.
Comment 4 Andrew Crouthamel 2018-09-25 21:40:16 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 03:32:34 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!