Hmmm, this worked for me on localhost Firefox latest. .
.wmd-image-button::before {
content: "\f030";
}
Maybe a one colon vs. two colons thing?
Hmmm, this worked for me on localhost Firefox latest. .
.wmd-image-button::before {
content: "\f030";
}
Maybe a one colon vs. two colons thing?
:before is css2, it should work AFAIK, but yes the correct syntax is ::before
Iâm sorry but I feel the need to call this out because it feels like a blatant contradiction.
I donât agree that itâs currently hidden, in your case youâve opted to expand the functionality of uploads, so Discourse has intelligently changed the icon to reflect this.
Agreed, some services do provide a little image button to upload images, particularly those which exclusively offer the ability to upload images, which Discourse did by default and you moved away from. Still, user choice and all that.
Wait, what?
Your initial assertion was that Discourse doesnât make uploads obvious enough, although I think we can agree from the above that it does until you change the default behaviour. Your criticism was that uploads werenât clear, but again until the default is changed itâs at least equal to that of other services. Youâve insisted that you need to keep other uploads enabled, but are now looking to conceal that functionality behind an image icon, effectively making that option much less obvious?
Donât get me wrong, youâre entitled to change it to any icon you want. Heck, you can use a if you so wish, but isnât it a little bizarre to make everything else less obvious instead of engaging in a tiny bit of user education?
TBH thatâs my feeling as well. If I were to be only allowing image uploads a camera icon might make more sense. But what of users wanting to upload text or PDF or whatever non-image?
Anyway, I was not offering any opinion as to the wisdom (or lack of) such decision, only offering a way.
Who knows, maybe it will work better?
Well, I think he has a point, but to me it is mostly about this:
If we decide we donât care about teaching formatting codes, can we have a simplified, task oriented editor with three big honking buttons instead of 11 tiny toolbar buttons?
It is basically these two things, opposed:
traditional formatted text editor toolbar design
simplified task-based plain text design
Sure Jeff, I get that, but the original point from Jesse was the assertion that uploading isnât obvious and that a file upload icon isnât clear for images, that they need some special case or dedicated button.
His use case apparently requires uploads of file types other than images, and is proposing a change that will ultimately make uploading those files less obvious.
Unless I missed something?
You could at least show them side-by-side using something like:
.wmd-image-button:before {
content: "\f030 \f093";
}
Iâm cringing even writing that, though.
Well, even changing the icon, picking this out
is harder than picking this out
Itâs just fundamental to âare we showing them 12 things to do, or three?â
Ok. Thanks for your feedback.
Iâm using your cringe-worthy code, thanks.
Also got it to work with #
instead of .
#wmd-image-button:before {
content: "\f030 \f093";
}
Ah, you must be a few versions behind then, as that change to .
was recent
Good to watch out for when I upgrade - thanks!
I agree that itâs a symptom of having a more complex editor more akin to word processing rather than social media⌠but it might be worth having two buttons in the instances of files other than images being allowed: the camera for images and the paperclip for other files?
It would probably be fine if they still opened the same upload dialogue, but it could make both actions clearer.
I like the paperclip over the up-arrow too.
I personally like the camera and paperclip idea. But Iâm biased because thatâs what Iâm doingâŚ
@mcwumbly in up arrowâs defense: Should attaching an image be more obvious?
However the paperclip is overwhelmingly used (life according to Google Images) when you search âattach iconâ
I think for a userâs understanding, âattachâ is probably a better verb and related icon than âupload.â
@awesomerobot is there an easy way to change the text area placeholder text and/or color? It doesnât appear that itâs possible with CSS? I was hoping to customize that for my installation too.
Ditto. âUploadâ makes sense if thatâs all youâre doing, but really youâre adding a file to a text message. AKA an attachment.
The placeholder text is set in the HTML, so the only way to override it in CSS is to hide it and use a :before (though maybe the composer input placeholder text should be a setting in the admin?)
So to hide the current text and display your own (in a custom color) youâd need
.wmd-input::-webkit-input-placeholder { color: #fff; }
.wmd-input::-moz-placeholder { color: #fff; }
.wmd-input:-ms-input-placeholder { color: #fff; }
.wmd-input::-webkit-input-placeholder:before { content: 'your content here'; color: salmon; }
.wmd-input::-moz-placeholder:before { content: 'your content here'; color: salmon; }
.wmd-input:-ms-input-placeholder:before { content: 'your content here'; color: salmon; }
@awesomerobot That seems to just add to the text, not replace it
Speaking of editing the text, the default seems to have the same âdrag or pasteâ explanation on mobile also. Not applicable on mobile, correct?