# \[BUG-13429\] Corner priority issue in tablet client

**URL:** <https://forum.inductiveautomation.com/t/bug-13429-corner-priority-issue-in-tablet-client/23360>\
**Category:** Ignition Early Access\
**Created:** [March 14, 2019, 8:03pm UTC](https://forum.inductiveautomation.com/t/bug-13429-corner-priority-issue-in-tablet-client/23360 "2019-03-14T20:03:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SMcIntosh](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SMcIntosh](https://forum.inductiveautomation.com/u/SMcIntosh)\
**Post date:** [March 14, 2019, 8:03pm UTC](https://forum.inductiveautomation.com/t/bug-13429-corner-priority-issue-in-tablet-client/23360/1 "2019-03-14T20:03:54Z")

</div>

The corner priority is set to top-bottom, and we have a header, footer, and left menu. When the menu is retracted and extended, it reappears over the footer view. This does not occur in a desktop client.

Android tablet, Chrome.

 ![_20190314_153539](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/de3639ad4e3157348f3a4391760e13eadca079a6.jpeg)

---

<div class="post-metadata">

**Author:** ![mperkins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mperkins/32/71722_2.png) [@mperkins](https://forum.inductiveautomation.com/u/mperkins)\
**Post date:** [April 2, 2019, 7:43pm UTC](https://forum.inductiveautomation.com/t/bug-13429-corner-priority-issue-in-tablet-client/23360/2 "2019-04-02T19:43:08Z")

</div>

Thank you for the report. I have reproduced this issue, and have created an internal ticket to be prioritized.

---

<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:** [April 26, 2019, 4:53pm UTC](https://forum.inductiveautomation.com/t/bug-13429-corner-priority-issue-in-tablet-client/23360/3 "2019-04-26T16:53:57Z")

</div>

This issue was fixed in the nightly 8.0.2 build that was uploaded today (4/26).
