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

Issue #848 - improve layout CSSFixme #891

Merged
merged 6 commits into from
Dec 31, 2015
Merged

Issue #848 - improve layout CSSFixme #891

merged 6 commits into from
Dec 31, 2015

Conversation

magsout
Copy link
Member

@magsout magsout commented Dec 30, 2015

@hallvors
Copy link
Contributor

@magsout what does code that has been modified look like? See http://hallvord.com/temp/moz/cssfixme.php?url=http%3A%2F%2Fhallvord.com%2Ftemp%2Fmoz%2FcompatTesterTesting%2Fstyle.css for an example.

@hallvors
Copy link
Contributor

Very minor language point: I wonder if "CSS code" will be easier to understand than "CSS instructions"..?

@magsout
Copy link
Member Author

magsout commented Dec 30, 2015

@hallvors aaaaahh, ok, 👎 my bad... So, I return to the previous style for the <pre>, and I only highlights the strong elements

@magsout
Copy link
Member Author

magsout commented Dec 30, 2015

capture d ecran 2015-12-30 a 14 24 07
capture d ecran 2015-12-30 a 14 24 13

@hallvors @karlcow @miketaylr Which one do you prefer ?

@karlcow
Copy link
Member

karlcow commented Dec 30, 2015

@magsout The 1st one (at the top). Many thanks. Super travail!

@magsout
Copy link
Member Author

magsout commented Dec 30, 2015

@hallvors is it possible to detect if there is content in the <pre> element? If so, you could add a class is-active because by default, when there is no content we still see the style of the <pre> because of padding (which I can delete it, but it's less pretty)

@hallvors
Copy link
Contributor

We can certainly set an is-active style from the JS when inserting the generated code. Or just generate the PRE element too on the fly..? You can just add a DIV id=result-parent or something to put the generated PRE inside, I think that may be cleaner than toggling PRE style based on a class :)

@hallvors
Copy link
Contributor

(I also vote for the 1st one - much of the point is to show very clearly what we're changing and it's more obvious that way)

@magsout
Copy link
Member Author

magsout commented Dec 30, 2015

Or just generate the PRE element too on the fly..? You can just add a DIV id=result-parent or something to put the generated PRE inside, I think that may be cleaner than toggling PRE style based on a class :)

@hallvors looks good 👍

           - removed <pre> which is generated by the script
@@ -20,7 +28,13 @@
<button type="button" class="Button Button--default" id="btn_do_fixup">Add standard equivalents for prefixed CSS</button>
</div>
<div class="wc-CSSFixme-item">
<pre class="wc-CSSFixme-resultat" id="fixedcss"></pre>
<div id="js-CSSFixme"></div>

This comment was marked as abuse.

@magsout
Copy link
Member Author

magsout commented Dec 30, 2015

Ok, updated with the style for pre

@magsout
Copy link
Member Author

magsout commented Dec 30, 2015

build passed

@miketaylr
Copy link
Member

Same, top style looks great.

@hallvors
Copy link
Contributor

I sort of liked the way the code in the second screenshot stands out with the yellow background though.. I'm testing the JS changes now, when the background is plain it is too much a part of the page, somehow. What about adding for example

.wc-CSSFixme-resultat{
  border-left: 8px solid var(--wc-background-dark);
  padding-left: 5px;
}

To make it stand out a bit more?
/me dabbling in designy stuff - feel free to ignore suggestions that betray my lack of taste :p

@hallvors
Copy link
Contributor

@magsout I hope you're happy with me pushing directly here..?

@magsout
Copy link
Member Author

magsout commented Dec 31, 2015

@hallvors I added the changes to the style. What makes good

capture d ecran 2015-12-31 a 07 44 27

@magsout I hope you're happy with me pushing directly here..?

it's fine to like that .. 👍

I'm reading your email and try to understand the issue

@miketaylr
Copy link
Member

It's only a global because the script for some reason is included twice in the page

I'm about to push a fix for that. I don't understand 100%, but the extrascripts template block was included inside the body template block, and I guess it looped over itself... twice? I don't know. But moving extrascripts outside of body (like all the other templates) fixes it. Pushing fix now.

(This fixes a double script include bug)
@magsout
Copy link
Member Author

magsout commented Dec 31, 2015

👍 @miketaylr

1 similar comment
@magsout
Copy link
Member Author

magsout commented Dec 31, 2015

👍 @miketaylr

@miketaylr
Copy link
Member

👍 👍 ^_^

@magsout
Copy link
Member Author

magsout commented Dec 31, 2015

oups .. ;)

@magsout
Copy link
Member Author

magsout commented Dec 31, 2015

Awesome.

@hallvors or @karlcow if everything looks good;)

@hallvors
Copy link
Contributor

Great, now we can undo the global-ness of that variable. If I do that quickly enough perhaps I can make it before Mike merges ;)

@hallvors
Copy link
Contributor

and @magsout 👍 to the extra styling - stands out now

@miketaylr
Copy link
Member

Heh, I'll let you pull the merge trigger @hallvors -- and I can deploy this afternoon as well.

@miketaylr
Copy link
Member

Great work @magsout and @hallvors!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants