Skip to content

[css-boxmodel] Totally missing one logical element. #1873

@Array23

Description

@Array23

Hello, I want to say, that you all did great job, on what web is today...
But I'm missing one thing as coder of webdesigns, that thing is simple css...

Inner Border
It's inner-borderattribute, as it states, that would be border, between padding and total size of box.
I want way to borders to not stack up in total size of element, because then I need to use calc() on basically everything.

I'm already working on polyfill, that takes whole css, and where i have --inner-border it wraps it to have height defined as calc(height -border);

#formbox { width: calc(100% / 6); border: 1px solid black; padding: 4px; }

This is what I've found on Mozilla, if I put 6 pieces of something like this, there would be overflow, because of 1px border...

But that won't make it part of something, official, I think two borders are no big issue, to be solved out...
Keep the original border doing what it is doing, and add inner border between padding and size on box model.

Sorry if this is not an 'issue' for you, but It makes coding of certain designs much more simple.

What's non-member patent licencing commitment? Can you explain? If you have no soul just steal this and implement it, otherwise explain to me how to fill for 'patent'. I'm struggling with issues about intellectual property.

Outer Padding
Also we could apply outer-padding which would be space between inner-border and padding...

Edge
And there could be a property of 'edge' which would apply on total edges of whole box(not containing original border)...

So I could set up an height and width of edge, and load for example image or svg into it like into a background.

It could be set up, so content would start after padding, or after edge, if edge overflowed, but preferred option it would be where the padding starts...

I'm working on some JavaScript that will work like this, but maybe a week it will be done, I just wanted to you to be aware of this by the October 30.

Why?

Just to create by pure html and css, without unnecessary JavaScript interface, where edges of elemets are dots and are connected to each other by line...

It can be done with more boxes, and a bunch of calc() but this seems to be better solution...

box-fill
I think in backend, there is something, that fills those boxes, it would fill the whole box, by it's size defined by size, and inner border would be overlay...

Also if I could make multiple layers of this box fill and merge them like I can do when I overlay individual divs like layers in gimp, would be very reasonable for easy to make irregular background, because I know everybody is being tired of simple patterns or just one color... I want to achieve something like irregular noise on the background. With this it wouldn't be that much for processor as overlaying multiple boxes I think.

It's better to do it once, and for all than every time somebody needs that

Even thou I have possibility of writing JavaScript for everything I said and do multiple boxes, I think it's good if it would be just standing in basic definition viable for everybody...

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions