Skip to content

bug: ion-label inside ion-item aligns wrongly or disappers if custom Angular component is used in this ion-item when stacked or floating position is set #22736

Closed

Description

@MaximS

ion-label inside ion-item aligns wrongly or disappers if custom Angular component is used in this ion-item when stacked or floating label position is set - because item-label-stacked class is not set on ion-item

Ionic version:

[x] 5.x (Angular project)

Current behavior:
When custom Angular component is used inside ion-item a class item-label-stacked is not set on ion-item if there is a label with position="stacked" inside that ion-item. (When built-in Ionic components like ion-input are used the ion-item gets this class automatically)

Expected behavior:
item-label-stacked class should be set on ion-item regardless of component used after the label

Steps to reproduce:
See Related code

Related code:
See stackblitz link
In a demo item-label-stacked is explicitly added to an ion-item. If it's removed than the label aligns itself to the left like position="fixed" or disappers completely if all the chips are deleted (using red crosses). See comments in tabs/tab1.page.html

Activity

  1. ionitron-bot commented on Jan 5, 2021

    @ionitron-bot

    Thanks for the issue! This issue has been labeled as holiday triage. With the winter holidays quickly approaching, much of the Ionic Team will soon be taking time off. During this time, issue triaging and PR review will be delayed until the team begins to return. After this period, we will work to ensure that all new issues are properly triaged and that new PRs are reviewed.

    In the meantime, please read our Winter Holiday Triage Guide for information on how to ensure that your issue is triaged correctly.

    Thank you!

  2. added
    type: buga confirmed bug report
    and removed
    holiday triageissues that were created during holiday period
    on Nov 15, 2021
  3. liamdebeasi commented on Aug 2, 2022

    @liamdebeasi
    Contributor

    Hi there,

    We are proposing some changes to form components that seek to resolve this issue. We would love your feedback on these proposed changes! You can read more about the changes and leave comments here: #25661

  4. added
    type: buga confirmed bug report
    and removed
    type: buga confirmed bug report
    on Nov 14, 2022
  5. added a commit that references this issue on Nov 15, 2022
    44472ae
  6. liamdebeasi commented on Nov 15, 2022

    @liamdebeasi
    Contributor

    Thanks for the report. In Ionic 7 we will be introducing a new syntax for using form components such as ion-input. You can find a summary of the changes here: #25661

    The reported issue is fixed with this new syntax. Work to update ion-input to use this new syntax has been completed, so I am going mark this issue as resolved. We plan to have a public beta period for Ionic 7 in the future. You can visit the Ionic Blog, Ionic Twitter, or our GitHub Releases Page to be notified when the Ionic 7 beta is released. Let me know if you have any questions. Thanks!

  7. ionitron-bot commented on Dec 15, 2022

    @ionitron-bot

    Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.

  8. locked and limited conversation to collaborators on Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions