Submit bug reports from your Help Menu. This is a user-to-user forum.
I cannot reproduce your issues in CC 2019. This code does not flag any errors or warnings for me. That said, a missing right brace is often caused by an unclosed media query higher up in the document or some other code error. Validate your complete CSS code with this online service.
The W3C CSS Validation Service
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>TEST</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<style>
body {
background-color: black;
color: white;
margin: 0 auto;
}
nav {
display: flex;
justify-content: space-around;
background-color: darkred;
}
nav a {
color: white;
padding: 10px;
}
#intro {
display: grid;
grid-template-columns: repeat(12, 1fr);
grid-template-rows: repeat(3, 1fr);
height: 90vh;
background-color: #202020;
}
#intro div {
grid-column: 1 / 5;
grid-row: 2;
background-color: red;
}
</style>
</head>
<body>
<header>
<nav>
<a href="#">Home</a>
<a href="#">About</a>
<a href="#">Events</a>
<a href="#">Contact</a>
</nav>
</header>
<main>
<section id="intro">
<div>Testing</div>
</section>
</main>
</body>
</html>
Submit bug reports from your Help Menu. This is a user-to-user forum.
I cannot reproduce your issues in CC 2019. This code does not flag any errors or warnings for me. That said, a missing right brace is often caused by an unclosed media query higher up in the document or some other code error. Validate your complete CSS code with this online service.
The W3C CSS Validation Service
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>TEST</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<style>
body {
background-color: black;
color: white;
margin: 0 auto;
}
nav {
display: flex;
justify-content: space-around;
background-color: darkred;
}
nav a {
color: white;
padding: 10px;
}
#intro {
display: grid;
grid-template-columns: repeat(12, 1fr);
grid-template-rows: repeat(3, 1fr);
height: 90vh;
background-color: #202020;
}
#intro div {
grid-column: 1 / 5;
grid-row: 2;
background-color: red;
}
</style>
</head>
<body>
<header>
<nav>
<a href="#">Home</a>
<a href="#">About</a>
<a href="#">Events</a>
<a href="#">Contact</a>
</nav>
</header>
<main>
<section id="intro">
<div>Testing</div>
</section>
</main>
</body>
</html>
https://forums.adobe.com/people/Jon+Fritz+II a écrit
Personally, I turned off Linting as soon as Adobe changed it from firing "on change" to "on save" only (after CC2015). In my opinion, it's pretty much useless if you have to save the page to be warned about an error.
100% agree with you, we had this discussion a while ago, and it was amazing how many users (from this forum) was arguing that "on save" was the best option... 
Hello Paula,
I could if necessary find these discussions in the archives (I consult the forum from a mailbox that collects each mail)...but now, I don't remember who, or how many users advocated that activating the lint was preferable when saving the document, and not during writing.
but free to name themselves here, and now, I am sure that some of them must be attentive to this discussion... 
as usual, in that thread that I remind we was like a handful to go from our respective and divergent points of view....
never mind
the idea of resuming a discussion to rebuild the world, why not... but only if folks @Adobe join us willingly, (and without wanting to hurt anyone, folks who can act and interact between us and the decision-makers.), ... otherwise it will be once again to get together to blow in the wind
I wasn't expecting a PM... a folks @Adobe will good enought... but no one answer... nor a PM nor a folks... so Adobe don't read anything down there... 
(one can speak loud so)....
You should also read -
https://forums.adobe.com/thread/2628371
I know we keep going over these subjects, time and time again, but
hello Preran,
I knew you were in the area... and I found a way to get you on stage...
Thank you for coming and being present
so... maybe we could start a new thread around all these topics, but the very first start, will probably to be informed about the DW future... what are the indoor objectives... may be having a PM around... so... if you don't mind.
have a pleasant weekend
birnou
Hello Preran,
Any news since our last conversation ?
Do you think there is a chance that a real exchange can be opened with the people in charge of Dreamweaver (PM but not that, I am also thinking of the person in charge of the web suite in general, decision-makers in terms of orientation in terms of tools for the web @Adobe...)
as Paula mentioned, I don't think a Roadmap is of any interest.
Dreamweaver is no longer a tool like the Dreamweaver flagship of the Macromedia fleet used to be. It is really time, now (if it is not too later) to rethink its orientations, its usefulness, and its positioning in the face of innumerable competition of tools, whether it is IDE, integrated tool (on or offline) and editor code.
so do you think such a discussion could take place?
Anyway, take good care, have a pleasant day and sorry for such pressure... 
birnou
).
AdChoices