Skip to content

[css-multicol] Referring to the multicol element / container #1965

Closed

Description

@rachelandrew

In the current multicol Working Draft the element that has column-count or column-width applied is referred to as the multicol element. In the discussions at TPAC @fantasai noted there is some confusion around what we call this element.

I noted that people were often referring to it as the multicol container in the meeting, which matches how we talk about flex and grid containers.

The current definition is here.

It seems that it would make sense to describe the multicol element/container in the same way as flex and grid, raising this issue for discussion of that.

Activity

  1. self-assigned this
    on Nov 9, 2017
  2. frivoal commented on Nov 11, 2017

    @frivoal
    Collaborator
  3. rachelandrew commented on Nov 12, 2017

    @rachelandrew
    ContributorAuthor

    Yes, essentially editing mention of element to container where it is used in this context.

    Is this something we need to bring to a meeting? If so I could add it to the agenda for the next call.

  4. FremyCompany commented on Nov 21, 2017

    @FremyCompany
    Contributor

    +1

  5. jensimmons commented on Nov 21, 2017

    @jensimmons
    Contributor

    I’m all for this. “Container” is now the defacto word for a parent element where the formatting context / layout method is changed. Multicolumn element sounds old and out of date. Multicolumn container sounds like “hey maybe I should take a look at that thing again.”

    +1

  6. astearns commented on Nov 21, 2017

    @astearns
    Member

    I'm happy to bring this up on a call and get a resolution for this, but I think in general a resolution should not be required for this kind of change. I'm assuming there is no normative requirement for implementations being modified here - it's just spec terms we're changing for clarity.

    (and I'm +1 as long as well all agree never to coin a 'multicoltainer' term)

  7. css-meeting-bot commented on Nov 22, 2017

    @css-meeting-bot
    Member

    The Working Group just discussed Referring to the multicol element / container, and agreed to the following resolutions:

    • RESOLVED: Use multicolumn container in the draft
    The full IRC log of that discussion <dael> Topic: Referring to the multicol element / container
    <dael> github: https://github.com//issues/1965
    <rego> no interop at all on this last issue; checking edge, chrome and firefox each one has a different output
    <dael> rachelandrew: This is...it poss doesn't need a resolution. When we disucssed at the F2F fantasai noted there's confusion as to what we call the element. I'm proposing we call it the multicol container which matches flexbox or grid.
    <dael> rachelandrew: I wanted to check if there are problems.
    <dael> fantasai: I think it's a necessary change. It's not an element, it's a box.
    <dael> rachelandrew: Cool. If people are happy, I'm working through the spec so this seemed the right time.
    <dael> astearns: Comments or concerns?
    <dael> Rossen_: Sounds like a good change.
    <tantek> +1
    <dael> astearns: Objections to using multicolumn container in the draft?
    <dael> RESOLVED: Use multicolumn container in the draft
    <dael> fantasai: new topic...back to grid.
  8. fantasai commented on Jun 8, 2018

    @fantasai
    Collaborator

    Hi @rachelandrew, Tab and I made a couple changes to complete this issue (letting you know for future reference, if you need to change an exported term):

    • We added an oldids attribute to the <dfn> for multi-column container so that old links to that definition won't break with the terminology change.
    • We update all the other specs in the repository (except for css-box and css-template which are unmaintained and outdated) to refer to the new terms.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions