# \[BUG-13507\] Microsoft Edge foot covers bottom of view

**URL:** <https://forum.inductiveautomation.com/t/bug-13507-microsoft-edge-foot-covers-bottom-of-view/23938>\
**Category:** Ignition Early Access\
**Created:** [April 8, 2019, 8:32pm UTC](https://forum.inductiveautomation.com/t/bug-13507-microsoft-edge-foot-covers-bottom-of-view/23938 "2019-04-08T20:32:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nburt](https://avatars.discourse-cdn.com/v4/letter/n/2bfe46/32.png) [@nburt](https://forum.inductiveautomation.com/u/nburt)\
**Post date:** [April 8, 2019, 8:32pm UTC](https://forum.inductiveautomation.com/t/bug-13507-microsoft-edge-foot-covers-bottom-of-view/23938/1 "2019-04-08T20:32:23Z")

</div>

In Chrome I don’t have this issue but testing my project on Edge I get about 70px of the bottom of my Views cut off which I can see is right behind my footer. This only seems to happen when I have a breakpoint container with an embedded view with useDefaultViewHeight = True, not when it equals false.

I can send screenshots but I’d prefer not to post them publicly.

8.0.0 (b2019040718)

---

<div class="post-metadata">

**Author:** ![osolorzano](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/osolorzano/32/6432_2.png) [@osolorzano](https://forum.inductiveautomation.com/u/osolorzano)\
**Post date:** [April 8, 2019, 9:29pm UTC](https://forum.inductiveautomation.com/t/bug-13507-microsoft-edge-foot-covers-bottom-of-view/23938/3 "2019-04-08T21:29:15Z")

</div>

I was able to recreate this issue. I’ll make an internal ticket for it.

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [May 8, 2019, 4:26pm UTC](https://forum.inductiveautomation.com/t/bug-13507-microsoft-edge-foot-covers-bottom-of-view/23938/4 "2019-05-08T16:26:00Z")

</div>

This issue was fixed in the nightly build that was uploaded today (5/8).
