facebookarchive/draft-js

'video' component in 'media' example looks odd in Safari/Firefox

Open

#1,310 opened on 2017年7月28日

GitHub で見る
 (3 comments) (0 reactions) (0 assignees)JavaScript (22,554 stars) (2,646 forks)batch import
bugdocumentationfirefoxhelp wantedsafari

説明

Do you want to request a feature or report a bug? This is a bug in the following example file: https://github.com/facebook/draft-js/blob/master/examples/draft-0-10-0/media/media.html

What is the current behavior? Steps to reproduce:

  1. Open the 'media.html' file in Firefox or Safari.
  2. Click 'Add Video'.
  3. Enter 'media.mp4' in the text input.
  4. Notice that the video component looks weird. See attached screenshot.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/stopachka/m6z0xn4r/.

What is the expected behavior? It should not have a semi-transparent area or hang out of the Draft composer area.

Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js? Safari/Firefox with the latest Draft on the master branch. screen shot 2017-07-28 at 9 20 32 am

コントリビューターガイド

技術スタック
reactjavascriptcsshtml
領域
frontend
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
under 1 hour
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
CSSbrowser dev toolsDraft.js basics
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
70
調査方針
Investigate the CSS styling of the video component in the media example file (media.html) by using browser developer tools in Safari and Firefox to identify which CSS properties cause the semi transparent area and misalignment. Then propose a fix that ensures consistent rendering across browsers, likely by adjusting positioning or opacity settings. Since the repository is archived, consider forking and addressing the issue in a fork or checking if there are any alternative solutions in the Draft.js community.