fujaba/NetworkParser

View on GitHub

Showing 4,645 of 4,645 total issues

Using height with border can sometimes make elements larger than you expect.
Open

    border: 1px solid #c2e1f5;

Rule doesn't have all its properties in alphabetical order.
Open

.CodeView {

Rule doesn't have all its properties in alphabetical order.
Open

.vkbuttonSpace:hover {

Rule doesn't have all its properties in alphabetical order.
Open

.diagram {

Rule doesn't have all its properties in alphabetical order.
Open

.Error {

Using width with border can sometimes make elements larger than you expect.
Open

    border: 1px solid #c2e1f5;

Using height with padding-bottom can sometimes make elements larger than you expect.
Open

    padding-bottom: 5px;

Rule doesn't have all its properties in alphabetical order.
Open

.SVGClazz-drawedge > rect{

Rule doesn't have all its properties in alphabetical order.
Open

.vkbuttonSpace {

Rule doesn't have all its properties in alphabetical order.
Open

.SVGChoice:hover {

Rule doesn't have all its properties in alphabetical order.
Open

#copyNode:hover circle{

Don't use IDs in selectors.
Open

#addEdge[visibility=visible] > circle{

Rule doesn't have all its properties in alphabetical order.
Open

.CodeView {

Using height with border can sometimes make elements larger than you expect.
Open

    border: 1px solid black;

Element (div.alt) is overqualified, just use .alt without element name.
Open

.ChoiceBox div.alt {

Rule doesn't have all its properties in alphabetical order.
Open

.lineElement {

Rule doesn't have all its properties in alphabetical order.
Open

.selection:hover {

Using width with border can sometimes make elements larger than you expect.
Open

    border: 1px solid #888;

Rule doesn't have all its properties in alphabetical order.
Open

.btnHideProp{

Rule doesn't have all its properties in alphabetical order.
Open

.SVGClazz-readyToConnect > rect{
Severity
Category
Status
Source
Language