if you create nested elements with with these styles, edge will crush

Fixed, not yet flighted Issue #5001390

Details

Created
Oct 13, 2015
Privacy
This issue is public.
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

==============

https://jsbin.com/lupurariqu

Expected Results:

==============

not to crush

Actual Results:

==============

Dev Channel specific:

================

No

 

Callstack:

00 edgehtml!Layout::ContainerBox::GetParentDisplayNodeForPositionedBox
01 edgehtml!Layout::ContainerBox::BuildDisplayNodesForSubtree
02 edgehtml!Layout::FlowBox::BuildDisplayNodesForSubtree
03 edgehtml!Layout::FlowBoxBuilder::ReuseChildBox
04 edgehtml!Layout::FlowBoxBuilder::BuildBoxItem
05 edgehtml!Layout::LayoutBuilderDriver::BuildPageLayout
06 edgehtml!Layout::PageCollection::FormatPage
07 edgehtml!Layout::PageCollection::LayoutPagesCore
08 edgehtml!Layout::PageCollection::LayoutPages
09 edgehtml!CMarkupPageLayout::CalcPageLayoutSize
0a edgehtml!CMarkupPageLayout::CalcTopLayoutSize
0b edgehtml!CMarkupPageLayout::DoLayout
0c edgehtml!CView::ExecuteLayoutTasks
0d edgehtml!CView::EnsureView
0e edgehtml!CPaintController::EnsureView
0f edgehtml!CPaintBeat::OnBeat
10 edgehtml!CPaintBeat::OnVSyncMethodCall
11 edgehtml!GlobalWndOnPaintPriorityMethodCall
12 edgehtml!GlobalWndProc
13 USER32!UserCallWinProcCheckWow
14 USER32!DispatchClientMessage
15 USER32!__fnDWORD
16 ntdll!KiUserCallbackDispatcherContinue
17 USER32!ZwUserDispatchMessage
18 USER32!DispatchMessageWorker
19 EMODEL!CTabWindow::_TabWindowThreadProc
1a EMODEL!LCIETab_ThreadProc
1b iertutil!_IsoThreadProc_WrapperToReleaseScope
1c KERNEL32!BaseThreadInitThunk
1d ntdll!RtlUserThreadStart

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rico M.”

      Changed Steps to Reproduce

      Changed Assigned To to “Peter S.”

      Changed Assigned To from “Peter S.” to “IE S.”

      Changed Status to “Fixed, not yet flighted”

    • Hello,

      Thank you for providing this information about the issue. We confirmed the problem, and implemented a solution on a later build of Edge. We are resolving this issue as a duplicate of an existing internal bug report. We look forward to additional feedback you may have on how we can improve Microsoft Edge.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in