apache/royale-asjs

Layout issues in Royale (High Priority)

Open

#617 opened on 2019年12月11日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)ActionScript (381 stars) (120 forks)batch import
help wanted

説明

Issues in top,bottom,left,right,height,width properties Issues in Every File

Project Details are : https://paste.apache.org/cpo8y Test case is available on VDI. Go to Inventory from Select in Menu Go to Misc-> Cities from Setups in Menu File : com/dbz/modules/Common/dbzCitySetup.mxml In Royale : https://user-images.githubusercontent.com/42200979/70599750-cac1b100-1c0f-11ea-96b2-cfb1f59ac2a1.png

In Flex : image

Go to Inventory from Select in Menu Go to Documents-> Configure from Setups in Menu File : com/dbz/modules/Common/dbzDocumentSetup.mxml In Royale : https://user-images.githubusercontent.com/42200979/70599755-cf866500-1c0f-11ea-81b4-6f965d905e1d.png

In Flex : image

Go to Inventory from Select in Menu Go to Freight Rate from Setups in Menu File : com/dbz/modules/Common/dbzFreightRateSetup.mxml In Royale : image

In Flex : freightratesetup

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

技術スタック
なし
領域
frontend
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
Understanding of MXML layout propertiesFamiliarity with Flex/Royale UI components
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
The issue reports layout discrepancies between Royale and Flex for multiple setup screens (e.g., dbzCitySetup.mxml, dbzDocumentSetup.mxml, dbzFreightRateSetup.mxml). The contributor should clone the repo, open these files, and compare the Royale output to the expected Flex layout shown in screenshots. Focus on fixing top, left, width, height, and other layout attributes to match Flex behavior. Since the issue is broad, start with one screen and validate the fix against the provided images. If the test case mentioned (on VDI) is not accessible, reproduce the issue with a simpler standalone example.