Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option Title breaking in two line because applying wrong css for manage width #20337

Closed
ghoshsweta opened this issue Jan 16, 2019 · 19 comments · Fixed by #20339
Closed

Option Title breaking in two line because applying wrong css for manage width #20337

ghoshsweta opened this issue Jan 16, 2019 · 19 comments · Fixed by #20339
Assignees
Labels
Area: Frontend Component: Catalog Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@ghoshsweta
Copy link

ghoshsweta commented Jan 16, 2019

Option Title breaking in two line because applying wrong css for manage width

Preconditions (*)

  1. Magento 2.3.0
  2. PHP 7.2

Steps to reproduce (*)

  1. Login to admin panel
  2. Go in Catalog > product section
  3. Create new product and go to tab Customizable Options and click on Add option button
    and see first label Option Title (See screenshot shown)

Actual result (*)

w6xu66h

Expected result (*)

sol

@magento-engcom-team
Copy link
Contributor

Hi @swetacedcoss. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@swetacedcoss do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 16, 2019
@cedarvinda cedarvinda self-assigned this Jan 16, 2019
@magento-engcom-team
Copy link
Contributor

Hi @cedarvinda. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@cedarvinda
Copy link
Member

@magento-engcom-team give me 2.3-develop instance

@ghost ghost self-assigned this Jan 16, 2019
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Jan 16, 2019

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@ghost ghost added Progress: needs update Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Component: Catalog Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed and removed Progress: needs update labels Jan 16, 2019
@magento-engcom-team
Copy link
Contributor

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97659 were created

@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jan 16, 2019
@ghost ghost removed their assignment Jan 16, 2019
@ghost ghost added the Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release label Jan 16, 2019
@dipti2jcommerce
Copy link

Hi @engcom-backlog-nazar ,
Can You Please provide me testing instance.

@ghost
Copy link

ghost commented Jan 16, 2019

@dipti2jcommerce you can recheck on your local environment.

@ghost ghost added the Area: Frontend label Jan 16, 2019
@ghost
Copy link

ghost commented Jan 16, 2019

@magento-engcom-team give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @engcom-backlog-nazar. Thank you for your request. I'm working on Magento 2.3-develop instance for you

@amol2jcommerce
Copy link
Contributor

Hi @swetacedcoss

I can't reproduced it.

@cedarvinda
Copy link
Member

@amol2jcommerce It's Reproduced in my local system
http://i.imgur.com/wkFhhwu.png

@ghost
Copy link

ghost commented Jan 16, 2019

@magento-engcom-team give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @engcom-backlog-nazar. Thank you for your request. I'm working on Magento 2.3-develop instance for you

@magento-engcom-team
Copy link
Contributor

Hi @engcom-backlog-nazar, here is your Magento instance.
Admin access: https://i-20337-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@amol2jcommerce
Copy link
Contributor

Hi @cedarvinda

It's Not Reproduced in given instance.
2019-01-16_18-28_new product - products

@ghost ghost removed the non-issue label Jan 16, 2019
@ghost ghost closed this as completed Jan 16, 2019
@ghost
Copy link

ghost commented Jan 16, 2019

@amol2jcommerce thank you

@ghost
Copy link

ghost commented Jan 16, 2019

@amol2jcommerce please recheck this issue on tablet view
selection_268

@cedarvinda
Copy link
Member

I am checking 1366 x 768 resolution device Its reproduced.
If it's on tablet view, should be fixed.

@cedarvinda cedarvinda reopened this Jan 16, 2019
@ghost ghost added the Progress: PR Created Indicates that Pull Request has been created to fix issue label Jan 16, 2019
irajneeshgupta added a commit to irajneeshgupta/magento2 that referenced this issue Jan 19, 2019
@magento-engcom-team
Copy link
Contributor

Hi @swetacedcoss. Thank you for your report.
The issue has been fixed in #20339 by @cedarvinda in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.2 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Mar 1, 2019
magento-engcom-team added a commit that referenced this issue Mar 1, 2019
…ause applying… #20339

 - Merge Pull Request #20339 from cedarvinda/magento2:Magento-2.3-develop-PR-15
 - Merged commits:
   1. 74b2098
   2. d7ba787
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Component: Catalog Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants