Skip to content

Suggest alternative approaches for .hidden and .show in migration docs #19789

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

Merged
merged 1 commit into from
May 9, 2016
Merged

Suggest alternative approaches for .hidden and .show in migration docs #19789

merged 1 commit into from
May 9, 2016

Conversation

lamby
Copy link
Contributor

@lamby lamby commented Apr 23, 2016

Signed-off-by: Chris Lamb [email protected]

@PauloFrancaLacerda
Copy link

.h, .s
:)

@lamby
Copy link
Contributor Author

lamby commented Apr 23, 2016

.h, .s

Hm? I don't see that on this branch.

@Lemmmy
Copy link

Lemmmy commented Apr 23, 2016

I would recommend .invisible first. Also, this file shows that there are .d-block, -d-inline-block and .d-inline, so they should be used instead of style="display: inline-block;" etc.

It may also be worth noting that .invisible sets the visibility to hidden, instead of display: none; like Bootstrap 3's .hidden did.

@takuhii
Copy link

takuhii commented Apr 23, 2016

.visible and .obscure ?
On 23 Apr 2016 11:27, "Drew Lemmy" [email protected] wrote:

I would recommend .invisible first.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#19789 (comment)

@lamby lamby changed the title Suggest a replacement to .hidden and .show [docs] Suggest alternative approaches for .hidden and .show Apr 23, 2016
@cvrebert cvrebert changed the title [docs] Suggest alternative approaches for .hidden and .show Suggest alternative approaches for .hidden and .show in migration docs Apr 24, 2016
@leetskills
Copy link

What about the hidden attribute?

@mdo mdo merged commit f278583 into twbs:v4-dev May 9, 2016
@mdo mdo added this to the v4.0.0-alpha.3 milestone May 9, 2016
@mdo
Copy link
Member

mdo commented May 9, 2016

Added @leetskills's suggestion, clarified the usage of those new options, and fixed some Markdown formatting in 72d68ba. Merged—thanks!

@mdo mdo mentioned this pull request May 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants