Anyone got a magnifying glass?
-
Discourse is a bit difficult to read without one...
And before you ask, browser zoom has no effect.
Also, F5 fixes it.
-
And again...
-
That's a new one. Which browser?
-
Firefox 34.0.5.
The issue is rather sporadic, but annoyingly frequent.
-
You are probably looking at a new experimental Heatmap-feature.
All content by TDWTF-Users gets downvoted (and becomes small) automatically. Which in this case is all content!
Filed Under: If we had Burn-Avatars, they would get small, too! | I could have put small-tags around this post but I refused to do so!
-
Or an experiment in removing unnecessary columns - surprised the avatar one still shows tbh.
-
Load thread from notification, and...
-
The <small> Thread is this way: →↗↪↜
-
Interesting...
It only happens when I open a Discolink in a new tab...
-
No repro in Chrome, even after disabling custom CSS.
-
AHA! Found the little bitch!
That CSS rule disappears when I refresh.
-
Has this happened before, say, 3 hours ago on the last update?
-
Has this happened before, say, 3 hours ago on the last update?
Wasn't happening yesterday, I know that much. Happened for the first time this morning; I logged on shortly after the update it seems.
-
Blame the update then - you aren't the only one seeing it...
-
It might be related to the changes discussed here:
https://meta.discourse.org/t/increasing-the-font-size/19346/9
Discoincreasing ⬆I am on my phone, so I am not going through the code changes.
-
This commit changed the following line:
This seems to produce the following CSS rule in the stylesheet:
html { font:0.875em/1.357em Helvetica,Arial,sans-serif; }
I’m under the impression that DiscoFox sometimes parses
0.875em/1.357em
as0.875em
, and other times as0.6448px
(or maybe there are other rules involved, I’m not sure).
-
a magnifying glass
At least you don't need them for new icons...
http://i.imgur.com/5DsGAYD.png
The star at the top is even so big it gets cut off:
-
Do we have a Mozilla bug number yet?
-
Do we have a Mozilla bug number yet?
Wonder what will come first - that or a birthday party:
http://www.youtube.com/watch?v=oAiVsbXVP6k
Filed under: the cake is a lie
-
-
Has it been deployed yet? I only ask because
And I like how the 'fix' doesn't actually involve the line causing the issue...
Maybe I spoke too soon; can't make it happen now...Yes I can...
-
Was only 'just in case it did.' Hard refresh probably required in either case.
-
And I like how the 'fix' doesn't actually involve the line causing the issue...
Well obviously, the way to fix stupid a broken hack is not to revert the stupid broken hack, but to make it even hackier.
-
Was only 'just in case it did.' Hard refresh probably required in either case.
Well, I cleared my browser cache, logged in again... and microtext.It seems Firefox is computing the erroneous size from a line that yields
-ms-text-size-adjust:100%;
in anhtml
selector.Well obviously, the way to fix stupid a broken hack is not to revert the stupid broken hack, but to make it even hackier.
Ah, so that's what I've been doing wrong the last 8.5 years!
-
I'm still wondering why text size has to be specified as a mathematical calculation at all. Why not just something like
.topic_title { font-size: 18pt; } .topic-text { font-size: 12pt; }
with an admin setting to change 'em?
-
Too simple. They probably chained together 32 different half-assed beta libraries to do whatever it is they're trying to do with the text size.
-
Too simple. They probably chained together 32 different half-assed beta libraries to do whatever it is they're trying to do with the text size.
I haven't browsed through all the code (the horror... the horror...), but what little I have seen, the CSS rules are full ofem
sizes specified to 3 or 4 decimal places.
-
I haven't browsed through all the code (the horror... the horror...), but what little I have seen, the CSS rules are full of em sizes specified to 3 or 4 decimal places.
Sounds like a tool.
When I was doing Silverlight, I could always tell when someone used Blend to layout a XAML view because the dimensions would be in pixels to 6 decimal places. My OCD forced me to go through and manually round all those to the nearest whole pixel. (I think I eventually wrote a script to do that for me.)
-
When I was doing Silverlight, I could always tell when someone used Blend to layout a XAML view because the dimensions would be in pixels to 6 decimal places.
At the risk of sounding like... him... that does smack of Doing It Wrong™. I always found it easier to let Silverlight's layout engine do the job it was designed to do, and use manually-set explicit sizes only to help nudge it in the right direction. And I did it all in Blend (with a little clean-up after in VS, normally just prettifying the XAML and removing all thed:
shite).
-
As soon as you resize something using the design view, it automatically switched to manually-set layout using pixel sizes.
Personally if I was working on stuff I hand-wrote all my XAML in Visual Studio, and it was 10x prettier than the vomit splatter created by the Blend designer.
-
Blend at least does make it easier to do databinding and storyboarding; you don't have to remember all the weird funky syntaxes and magic names and such. And you can preview the animations without going through a whole rebuild cycle.
-
Personally if I was working on stuff I hand-wrote all my XAML in Visual Studio
it's also not that complicated.
-
-
if you say so. i say elegant
-
if you say so. i say elegant
Not when you've learned Razor, it's notOK, Razor's not that much better, but it is far less verbose.
-
Interesting...
I've had it happen several times now:
It only happens when I open a Discolink in a new tab...- Search through Discourse using Google small text.
- Ctrl + MouseL to open link in new tab
- Following a link of an e-mail notification with "Open in new tab" all OK.
That's quite a disconsistency in the DisCoStyleSheet.
-
I technically have a repro in Chrome, but it looks like Chrome handles the issue a bit differently:
Looks like Firefox tries to make it something usable, Chrome just disregards it as invalid.
-
IE11 does the same thing:
-
I technically have a repro in Chrome, but it looks like Chrome handles the issue a bit differently:
Looks like Firefox tries to make it something usable, Chrome just disregards it as invalid.
Confirmed (Win 7, Chrome 39.0.2171.95 m)
-
So TRWTF is once again using Firefox
-
So TRWTF is once again using Firefox
Not really, font-size without a unit would be undefined behavior and Firefox is unleashing the nasal demons.
-
ever since 3.5 it's been going down hill. since google dropped their funding contract it's turned from a glide to a dive off a cliff.
but that's just my NSHO
-
ever since 3.5 it's been going down hill.
Meh, all software goes through 30+ lousy versions in a row at some point doesn't it?
The only reason I still use Firefox is that Firebug is much easier to use than the Chrome Developer console for me.
-
The only reason I still use Firefox is that Firebug is much easier to use than the Chrome Developer console for me.
that's what kept me on FF for a long time.
then i got fed up with FF to the point i said "FRACK IT! i'm actually sitting down and LEARNING the chrome develoepr console."
after about three hours of activly trying to use it and find all the buttons it was much better to use.
-
So I had 2 new posts in this thread, it should open to post 43. Instead, it opens to post 16.
-
@chubertdev - Days Since Last Discourse Bug: 0
-
So I had 2 new posts in this thread, it should open to post 43. Instead, it opens to post 16.
That's because they wanted to increase post count so they made the thread open to $latest_post/$posts_per_screen
-
Loaded to post 20 this time...
-
-
http://what.thedailywtf.com/t/docker-upgrades/1929/116?u=pjh
Better, but still doesn't actually address the root cause...