⢈⠤⢣⡑ ⡬⢻⡍⢸⢵⣤ ⢎⡀⣈ (invalid title)
-
Continuing the discussion from The Official "Likes" Thread - 1325 minutes (and counting) of reading fun. And now with 282016 likes!:
⢁ ⡑⢛⢿⠊⢳⠔⣹ ⢡⡼⡠⠋ ⢬⣄⡽⡰⣉⢒ ⠩⢎⢊⣭⠘⣹⠤⠛⣛⡐ ⢹⢛⠝ ⠻⣭⢸⣺⣸ ⡬⠏⣱⠎⢋⡑⠚ ⠷⠖⢗⢨⣟⠩ ⣑⡭⢳ ⢾⢅⢬⣣⢡⢈⠴⡚⠤ ⡑⢖⠑⠊⢐⠉ ⡷⢟⣻⢅⠫⡍⢟⡣⡣ ⠶⠋⡂⡟ ⣝⢰⠘⣻⡋⣺⢖ ⣖⢊⣤⢕⣲⣁⣄⠝⣬⣞⣫⡰⠮⠒⣡ ⢶⢵⠪⠷⢞ ⠻⢈⠤⢣⡑ ⡬⢻⡍⢸⢵⣤ ⢎⡀⣈⠣
actually @riking said that, @failbag just quoted it (the other failbag.)
-
dunno @faoileag, looks like it works to me.
-
I'm running my fingers along the screen, but it's not working!
-
You should 3D-print it and place it on a wooden table before reading.
-
dunno @faoileag, looks like it works to me.
Figured it out: taking @riking's full string as topic title causes internal server errors, taking an abbridged versions works.
-
WTF Chrome, Windows, whoever fucks this up ...
I can accept that you don't display those characters but this ...
You can obviously display it in the title then why not on the page ...
-
Chrome and Unicode have the weirdest relationship.
-
Mobile Chrome just shows nothing so it looks like the topic title is blank.
-
Ikr
-
WTF Chrome, Windows, whoever fucks this up ... I can accept that you don't display those characters but this ...
Conway's Life in the titlebar? Impressive.
-
Also: I'm sure it gives people hives to realize that IE gets it right and displays the Braille in the window as well as the title bar.
-
I can accept that you don't display those characters but this ...
Chrome can also display those characters in the URL bar
ANNOYING: their patch for the Quote highlight button to make the " portion clickable makes the " touch against the Quote Reply text in the button:
BUG: if someone posts something while you're trying to Quote Reply, that post steals your focus and unhighlights your text. THANKS DICSOURSE.
-
their
You mean my patch for how it was, now interfering with how it is.
@PJH, you can remove the
.quote-button:before
style, since the Discourse devs effectively used what we did for their fix to that issue. Of course, I personally wouldn't have just added padding characters in content, but used a margin, but what do I know, right?
-
I didn't apply your patch here on this computer.
edit - oh nevermind, PJH made it global? got it.
-
I didn't apply your patch here on this computer.
PJH added it to the site styles, so everyone has it. Since the Disco devs changed how that works, now the patch makes it look bad since they didn't use a margin, but have spaces in the "content":
.quote-button:before { font-family: "FontAwesome"; content: "\f10e\00a0\00a0"; }
That's their "fix". What I would've done:
.quote-button:before { font-family: "FontAwesome"; content: "\f10e"; margin-right: 8px; }
Which means if anyone wants to override the icon, they don't have to make sure they get the spaces as well.
Though if you wanted to get rid of the icon, you'd have to override the margin as well. Either or is likely an edge case, but personally I see using spaces for that padding as bad design.
-
They appear to have fixed clicking the quote symbol anyway - I've removed the display:none as well and it seems to be working here...
Tested FF 24.7, 35.0, Chrome 37.
-
They appear to have fixed clicking the quote symbol anyway
They did it the same way I effectively did, by removing the element that was inside the quote reply button that contained the quote symbol originally and just putting the quote symbol on a
::before
in the quote reply button itself.
-
personally I see using spaces for that padding as bad design.
You and everyone else that isn't terrible at CSS TBH.
-
-
Why is this shit not in the 1-hour post (or whatever the category is) I have ignored?
-
We could move it to the lounge!
-
He could move it to the.... oh, wait...
-
For reference, here's how I generated the text:
<Riking> ?+braille <Shocky> braille: <alias>randchar %arg0% 10240 10495 <Riking> ?+randchar <Shocky> randchar: <php>if ($argc < 3) die(); $i = intval($arg[0]); $i = min(max($i,8),100); while ($i-- > 0) echo mb_convert_encoding("&#".rand(intval($arg[1]),intval($arg[2])).';','UTF-8','HTML-ENTITIES'); <Riking> ?braille 32 <Shocky> ⢏⠿⠀⠭⠪⠃⣢⢱⣖⡌⣻⣹⢊⣜⢰⠢⠏⠸⣟⡇⡔⢣⢣⠿⣠⢷⡅⢝⣛⠽⢍⡪ <Riking> ?+cjk <Shocky> cjk: <alias>randchar %arg0% 19968 40959 <Riking> ?cjk 32 <Shocky> 檱箷媔鿞选兀郅非鏧诠哤树讏憋碱獳羻唎钟庙熟颽媪强蔂墩憴悹足審蕨塤
...the argument order for mb_convert_encoding is pretty wacked. String, To, From? seriously?
-
BUG: if someone posts something while you're trying to Quote Reply, that post steals your focus and unhighlights your text. THANKS DICSOURSE.
Could be the third observed bug today...
-
Half the stuff in PHP for things like that is 'thing you're working on', 'thing you're doing to it' (preg_match, preg_replace etc.) and mb_convert_encoding falls into that, just as iconv does. Other things like substr too.
Then you have all the other stuff where it doesn't, like str_replace which is 'from', 'to', 'target string' which is maddeningly unhelpful.
And then of course there's strpos vs in_array, which are haystack/needle and needle/haystack respectively.
-
Could be the third observed bug today...
I see "view older notifications" sends you to your activity page; which, e.g. does not include notifications for topics you're watching. Is that a new bug?
-
I see "view older notifications" sends you to your activity page; which, e.g. does not include notifications for topics you're watching. Is that a new bug?
No, that ones old. Here's the relevant topic over at meta.d. Doesn't really seem to be a high priority item for them.
-
Also: I'm sure it gives people hives to realize that IE gets it right and displays the Braille in the window as well as the title bar.
IE renders ActiveX correctly too. That doesn't make it better.
-
(1) new post in topic, (new) topic!
The fuck.