Skip to content

Solve the CSS class portability problem #43

@richard-jones

Description

@richard-jones

How can we deal with the issue where the change of a css class name requires a new or modified renderer.

For example, it would be quite good to have edges-specific classes only in edges, and no framework classes (e.g. no bootstrap rows, cols, etc). And then for them to be mapped onto the framework classes in some other layer.

This allows us to remain independent of the style framework, and to help us avoid clashes between host system classes and edges layout (e.g. row is a heavily overloaded style name)

Does such a mechanism exist? Or what could we do?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions