- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
在尝试使用 flexbox 制作有用的模态时,我发现似乎是浏览器问题,想知道是否有已知的修复或解决方法 - 或者关于如何解决它的想法。
我要解决的问题有两个方面。首先,让模态窗口垂直居中,这按预期工作。第二个是让模态窗口滚动——在外部,所以整个模态窗口滚动,而不是其中的内容(这样你就可以有下拉菜单和其他可以扩展到模态边界之外的 UI 元素——例如自定义日期选择器等)
但是,当将垂直居中与滚动条结合使用时,模态框的顶部会变得无法访问,因为它开始溢出。在上面的示例中,您可以调整大小以强制溢出,这样做允许您滚动到模态框的底部,但不能滚动到顶部(第一段被截断)。
.modal-container {
position: fixed;
top: 0;
left: 0;
bottom: 0;
right: 0;
background: rgba(0, 0, 0, 0.5);
overflow-x: auto;
}
.modal-container .modal-window {
display: -ms-flexbox;
display: flex;
flex-direction: column;
align-items: center;
justify-content: center;
/* Optional support to confirm scroll behavior makes sense in IE10
//-ms-flex-direction: column;
//-ms-flex-align: center;
//-ms-flex-pack: center; */
height: 100%;
}
.modal-container .modal-window .modal-content {
border: 1px solid #ccc;
border-radius: 4px;
background: #fff;
width: 100%;
max-width: 500px;
padding: 10px
}
<div class="modal-container">
<div class="modal-window">
<div class="modal-content">
<p class="p3">Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.</p>
<p class="p3">Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.</p>
<p class="p3">Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.</p>
</div>
</div>
</div>
这会影响(当前的)Firefox、Safari、Chrome 和 Opera。有趣的是,如果您在 IE10 供应商前缀 CSS 中发表评论,它在 IE10 中的行为确实正确——我还没有在 IE11 中进行测试,但假设该行为与 IE10 的行为相匹配。
这是示例代码的链接(高度简化)
最佳答案
Flexbox 使居中变得非常容易。
通过简单地将 align-items: center
和 justify-content: center
应用到 flex 容器,您的 flex 元素将垂直和水平居中。
但是,当 flex 元素大于 flex 容器时,此方法会出现问题。
如问题中所述,当 flex 元素溢出容器时,顶部将无法访问。
对于水平溢出,左侧部分变得不可访问(或右侧部分,在 RTL 语言中)。
这是一个包含 justify-content: center
和三个 flex 元素的 LTR 容器的示例:
有关此行为的解释,请参阅此答案的底部。
要解决此问题,请使用 flexbox auto margins ,而不是 justify-content
。
使用 auto
边距,溢出的 flex 元素可以垂直和水平居中,而不会失去对其任何部分的访问。
所以在 flex 容器上代替这段代码:
#flex-container {
align-items: center;
justify-content: center;
}
在 flex 元素上使用此代码:
.flex-item {
margin: auto;
}
将 safe
值添加到您的关键字对齐规则中,如下所示:
justify-content: safe center
或
align-self: safe center
来自CSS Box Alignment Module specification :
4.4. Overflow Alignment: the
safe
andunsafe
keywords andscroll safetylimitsWhen the [flex item] is larger than the [flex container], it willoverflow. Some alignment modes, if honored in this situation, maycause data loss: for example, if the contents of a sidebar arecentered, when they overflow they may send part of their boxes pastthe viewport’s start edge, which can’t be scrolled to.
To control this situation, an overflow alignment mode can beexplicitly specified.
Unsafe
alignment honors the specifiedalignment mode in overflow situations, even if it causes data loss,whilesafe
alignment changes the alignment mode in overflowsituations in an attempt to avoid data loss.The default behavior is to contain the alignment subject within thescrollable area, though at the time of writing this safety feature isnot yet implemented.
safe
If the size of the [flex item] overflows the [flex container], the[flex item] is instead aligned as if the alignment mode were[
flex-start
].
unsafe
Regardless of the relative sizes of the [flex item] and [flexcontainer], the given alignment value is honored.
注意:盒子对齐模块用于多个盒子布局模型,而不仅仅是 flex。所以在上面的规范摘录中,括号中的术语实际上是“对齐主题”、“对齐容器”和“开始
”。我使用特定于 flex 的术语来关注这个特定问题。
Flexbox's alignment properties do "true" centering, unlike othercentering methods in CSS. This means that the flex items will staycentered, even if they overflow the flex container.
This can sometimes be problematic, however, if they overflow past thetop edge of the page, or the left edge [...], asyou can't scroll to that area, even if there is content there!
In a future release, the alignment properties will be extended to havea "safe" option as well.
For now, if this is a concern, you can instead use margins to achievecentering, as they'll respond in a "safe" way and stop centering ifthey overflow.
Instead of using the
align-
properties, just putauto
margins onthe flex items you wish to center.Instead of the
justify-
properties, put auto margins on the outsideedges of the first and last flex items in the flex container.The
auto
margins will "flex" and assume the leftover space,centering the flex items when there is leftover space, and switchingto normal alignment when not.However, if you're trying to replace
justify-content
withmargin-based centering in a multi-line flexbox, you're probably out ofluck, as you need to put the margins on the first and last flex itemon each line. Unless you can predict ahead of time which items willend up on which line, you can't reliably use margin-based centering inthe main axis to replace thejustify-content
property.
关于html - 无法滚动到容器溢出的 flex 元素顶部,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/54680179/
我通过 spring ioc 编写了一些 Rest 应用程序。但我无法解决这个问题。这是我的异常(exception): org.springframework.beans.factory.BeanC
我对 TestNG、Spring 框架等完全陌生,我正在尝试使用注释 @Value通过 @Configuration 访问配置文件注释。 我在这里想要实现的目标是让控制台从配置文件中写出“hi”,通过
为此工作了几个小时。我完全被难住了。 这是 CS113 的实验室。 如果用户在程序(二进制计算器)结束时选择继续,我们需要使用 goto 语句来到达程序的顶部。 但是,我们还需要释放所有分配的内存。
我正在尝试使用 ffmpeg 库构建一个小的 C 程序。但是我什至无法使用 avformat_open_input() 打开音频文件设置检查错误代码的函数后,我得到以下输出: Error code:
使用 Spring Initializer 创建一个简单的 Spring boot。我只在可用选项下选择 DevTools。 创建项目后,无需对其进行任何更改,即可正常运行程序。 现在,当我尝试在项目
所以我只是在 Mac OS X 中通过 brew 安装了 qt。但是它无法链接它。当我尝试运行 brew link qt 或 brew link --overwrite qt 我得到以下信息: ton
我在提交和 pull 时遇到了问题:在提交的 IDE 中,我看到: warning not all local changes may be shown due to an error: unable
我跑 man gcc | grep "-L" 我明白了 Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help' for more inf
我有一段代码,旨在接收任何 URL 并将其从网络上撕下来。到目前为止,它运行良好,直到有人给了它这个 URL: http://www.aspensurgical.com/static/images/a
在过去的 5 个小时里,我一直在尝试在我的服务器上设置 WireGuard,但在完成所有设置后,我无法 ping IP 或解析域。 下面是服务器配置 [Interface] Address = 10.
我正在尝试在 GitLab 中 fork 我的一个私有(private)项目,但是当我按下 fork 按钮时,我会收到以下信息: No available namespaces to fork the
我这里遇到了一些问题。我是 node.js 和 Rest API 的新手,但我正在尝试自学。我制作了 REST API,使用 MongoDB 与我的数据库进行通信,我使用 Postman 来测试我的路
下面的代码在控制台中给出以下消息: Uncaught DOMException: Failed to execute 'appendChild' on 'Node': The new child el
我正在尝试调用一个新端点来显示数据,我意识到在上一组有效的数据中,它在数据周围用一对额外的“[]”括号进行控制台,我认为这就是问题是,而新端点不会以我使用数据的方式产生它! 这是 NgFor 失败的原
我正在尝试将我的 Symfony2 应用程序部署到我的 Azure Web 应用程序,但遇到了一些麻烦。 推送到远程时,我在终端中收到以下消息 remote: Updating branch 'mas
Minikube已启动并正在运行,没有任何错误,但是我无法 curl IP。我在这里遵循:https://docs.traefik.io/user-guide/kubernetes/,似乎没有提到关闭
每当我尝试docker组成任何项目时,都会出现以下错误。 我尝试过有和没有sudo 我在这台机器上只有这个问题。我可以在Mac和Amazon WorkSpace上运行相同的容器。 (myslabs)
我正在尝试 pip install stanza 并收到此消息: ERROR: No matching distribution found for torch>=1.3.0 (from stanza
DNS 解析看起来不错,但我无法 ping 我的服务。可能是什么原因? 来自集群中的另一个 Pod: $ ping backend PING backend.default.svc.cluster.l
我正在使用Hibernate 4 + Spring MVC 4当我开始 Apache Tomcat Server 8我收到此错误: Error creating bean with name 'wel
我是一名优秀的程序员,十分优秀!