Conflicting Files Information Required NPM Resource Changed ? Pending

User tests: Successful: Unsuccessful:

avatar sksuryan
sksuryan
10 Mar 2021

Pull Request for Issue #31936.

Summary of Changes

This pull request fixes the inconsistent Joomla logo sizes in the headers of installation page and administrator page.

Actual result BEFORE applying this Pull Request

image
image

Expected result AFTER applying this Pull Request

image
image

avatar sksuryan sksuryan - open - 10 Mar 2021
avatar sksuryan sksuryan - change - 10 Mar 2021
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 10 Mar 2021
Category Installation NPM Change
avatar sksuryan sksuryan - change - 10 Mar 2021
Labels Added: NPM Resource Changed ?
avatar richard67 richard67 - change - 10 Mar 2021
Title
fixes inconsistent logo sizes
[4.0] fixes inconsistent logo sizes
avatar richard67 richard67 - edited - 10 Mar 2021
avatar drmenzelit
drmenzelit - comment - 10 Mar 2021

Thank you for your first PR in Joomla @sksuryan. @C-Lodder can you be so kind and explain our new contributor (GSoC student) what you mean with your comment? Thank you.

avatar sksuryan
sksuryan - comment - 10 Mar 2021

Thank you for your first PR in Joomla @sksuryan. @C-Lodder can you be so kind and explain our new contributor (GSoC student) what you mean with your comment? Thank you.

Thank you @drmenzelit, Glad to make my first PR to Joomla.

avatar drmenzelit
drmenzelit - comment - 17 Mar 2021

I can confirm that the svg logo has a transform="translate(10 0) scale(1.3)" defined... why? I have no idea...
But in the index.php from atum the logo is being inserted in an image tag and not as svg direct. Which way is better it is difficult to say, but we should be consistent.

avatar sksuryan
sksuryan - comment - 17 Mar 2021

image

for some reason, only this logo was being cut-off from all sides like this while rest images were fine but it is fine if I use it's source directly.

I realized that was because I was using img tag but since it's an svg I can directly import it and use it.

I can confirm that the svg logo has a transform="translate(10 0) scale(1.3)" defined... why? I have no idea...
But in the index.php from atum the logo is being inserted in an image tag and not as svg direct. Which way is better it is difficult to say, but we should be consistent.

Pushing new changes which should address this. It also changes px values in favor of rem.

avatar srishty-07 srishty-07 - test_item - 18 Mar 2021 - Tested successfully
avatar srishty-07
srishty-07 - comment - 18 Mar 2021

I have tested this item successfully on 0543574

I have tested it successfully on Joomla 4.0.0-beta-8-dev.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32632.

avatar Quy
Quy - comment - 23 Apr 2021

An alternative PR #33100.

avatar sksuryan
sksuryan - comment - 2 May 2021

An alternative PR #33100.

This PR actually adds the same logo to Installation UI as in the Admin UI since the previous logo in the Installation UI was much bigger. This PR doesn't change anything in the Admin UI itself.

avatar richard67
richard67 - comment - 6 May 2021

@sksuryan Do you really think someone will ever compare the logo sizes of the installation and the admin UI? To be honest, in my personal opinion this PR here is not really needed. But that's just my personal opinion, I don't have any right to decide ;-)

avatar sksuryan
sksuryan - comment - 6 May 2021

@richard67 I mean, an issue does exist for this

avatar brianteeman
brianteeman - comment - 6 May 2021

@richard67 consistency in branding is always good

avatar richard67
richard67 - comment - 6 May 2021

@sksuryan Not really a major issue, and sometimes we close issues as won't fix. But as said, that's not only my decision.

avatar richard67
richard67 - comment - 6 May 2021

consistency in branding is always good

@brianteeman Is the same brand, only different size, so not really inconsistent. And the PR adds another import of an SVG .. is that really worth the little benefit?

avatar Quy
Quy - comment - 6 May 2021

This has been fixed with PR #33100. Please install the latest version and confirm.

avatar brianteeman
brianteeman - comment - 6 May 2021

I am making no comment on how the code is changed ;)

If it was just an issue then closing as "wont fix" is fine and should be done much much much more often
But this is a PR.

If the PR works and meets standards etc then it should be considered.

if it has already been fixed elsewhere then of course it should be closed as there is nothing left to fix?

avatar alikon
alikon - comment - 6 May 2021

that issue is still present after merge of #33100 ?
anyway as per Conflicting files @sksuryan you should revisit your pr ;)

avatar sksuryan
sksuryan - comment - 7 May 2021

that issue is still present after merge of #33100 ?
anyway as per Conflicting files @sksuryan you should revisit your pr ;)

I'll take a look @alikon

avatar Quy
Quy - comment - 14 May 2021

Closing as this is no longer an issue. Thanks for the PR.

avatar Quy Quy - change - 14 May 2021
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2021-05-14 13:48:50
Closed_By Quy
Labels Added: Conflicting Files Information Required
avatar Quy Quy - close - 14 May 2021

Add a Comment

Login with GitHub to post a comment