Title of video doesn't hide if you use horizontal orientation when you click the share button
Please answer the following questions for yourself before submitting a question.
- [ ] I am running the latest version
- [x] I checked the knowledge base and found no answer
- [x] I checked to make sure that this issue has not already been filed
Ask a question
使用"AdGuard撥放器"播放影片,但影片標題無法隱藏
我是使用「Xiaomi 小米 電視盒子S (2代)」在用AdGuard撥放器觀看 在手機下,文字標題會跟下方的控制按 鍵 、進度條一起被隱藏 但是在電視盒的話,只有控制按鍵 、進度條 會隱藏,文字標題會一直顯示 不知道是不是Bug?還是不夠相容,請修正一下
google translate: I am using the "Xiaomi TV Box S (2nd Gen)" to watch using the AdGuard player Under the mobile phone, the text title will be hidden together with the control button and progress bar below. However, in the TV box, only the control button and the progress bar will be hidden, and the text title will be displayed all the time I don't know if it's a bug or it's not compatible enough, please correct it
Please describe in details or send a video how do you open and use AdGuard player on TV.
在TV上安裝Firefox(Firefox有同步書籤的功能比較方便) 使用Firefox的"分享"功能 選擇"AdGuard 播放器" 步驟跟手機一樣
後來我發現手機也是一樣的狀況 如果手機使用橫屏顯示,再去開啟AdGuard 播放器 標題列一樣不會自動消失,必須先轉成豎屏再轉回橫屏才可以隱藏 (當然!電視是不能轉的)
Google translate: Install Firefox on TV (Firefox has the function of synchronizing bookmarks more convenient) Use Firefox's "Share" feature Select "AdGuard Player" The steps are the same as the mobile phone
Later I found out that the same is true for the phone If the phone uses horizontal screen display, turn on the AdGuard player The title column will not disappear automatically. It must be converted to vertical screen and then turned back to horizontal screen before it can be hidden. (Of course! TV can't turn)
AdGuard for TV doesn't have a functionality - YouTube player. So we can't fix it. Also, there is no Firefox in Google Play on TV, which means you most likely installed the mobile version and that’s why there is a button to play the video in the AdGuard player. This possibility was not intended by our developers. Regarding the mobile version - we will fix this bug in the coming versions! Thank you for bringing this issue to our attention.