Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove zIndex property #4685

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from
Open

Conversation

dzonidoo
Copy link
Collaborator

SDESK-7429

triggerSelector="#marked-for-desks"
title={gettext('Marked for')}
title={gettext('Marked for 123123123')}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

restore the old string

@tomaskikutis
Copy link
Member

did you expose a function from ui-framework to get latest z-index when not using ui-framework components?

@dzonidoo
Copy link
Collaborator Author

but i dont need it for this pr...

@tomaskikutis
Copy link
Member

How likely it is that someone will need it later? Probably 100% :D Do expose it now(from ui-framework side) so others don't need to later.

@dzonidoo
Copy link
Collaborator Author

but this is ui framework side... i just need to export it.. why is that in relationship with this pr?

@dzonidoo
Copy link
Collaborator Author

do i need to bump version of ui framework again after exporting?

@tomaskikutis
Copy link
Member

fix ci

@tomaskikutis
Copy link
Member

@dzonidoo I've restarted unit tests, they do pass now, but there are issues with extensions - do take a look

@dzonidoo
Copy link
Collaborator Author

@tomaskikutis so do i need to reset the failed test?

@tomaskikutis
Copy link
Member

no, you need to fix the issues with extensions - see logs

@petrjasek
Copy link
Member

there are also some z-indexes in angular templates like here, should those be removed too? seems like it's causing some issues currently

@tomaskikutis
Copy link
Member

The reason why z-indexes were removed from react components is because we are handling z-indexes on ui-framework side. That only happens for react components though.

I think there are 2 options here @dzonidoo, either to initialize z-index on ui-framework side to a lower value so it doesn't conflict with angular z-indexes, or export that function from ui-framework to generate a next z-index and use it for angular components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants