[buddypress-trac] [BuddyPress Trac] #7210: Group type frontend integration
buddypress-trac
noreply at wordpress.org
Thu Oct 6 22:33:46 UTC 2016
#7210: Group type frontend integration
-------------------------+--------------------
Reporter: r-a-y | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 2.7
Component: Groups | Version: 2.6.0
Severity: normal | Resolution:
Keywords: has-patch |
-------------------------+--------------------
Comment (by hnla):
Replying to [comment:36 r-a-y]:
> > I don't really care what legacy templates do any longer they are dead
to me
>
> Are you referring to the group type directory message or the group type
list function? I don't mind if we make the change to the directory type
message, although the change is quite trivial.
>
> FWIW, `<strong>` vs. `<b>` - https://developer.mozilla.org/en-
US/docs/Web/HTML/Element/strong#Bold_vs._Strong
>
> {{{
>
> strong is a logical state, and bold is a physical state.
>
> Logical states separate presentation from the content, and by doing so
allow for it to be
> expressed in many different ways. Perhaps instead of rendering some text
as bold you want
> to render it red, or a different size, or underlined, or whatever.
>
> It makes more sense to change the presentational properties of strong
than it does bold.
> This is because bold is a physical state; there is no separation of
presentation and content,
> and making bold do anything other than bold text would be confusing and
illogical.
> }}}
>
> `<strong>` sounds like the correct use here, but I could be wrong.
No matter @r-a-y I'll work out what we need by way of ease of access to
these elements so we can change as see fit, I'll try and make a note on
Nouveau tickets about it.
fwiw I think that Mozilla ref sounds like gibberish tbh I would not say
''strong'' is correct nor do I understand what on earth they are on about
but in html5 they attempted to redefine semantics for all these elements
so to describe `b` as physical is not strictly correct, I do love Mozilla
& their MDN site but on this I think they need to review their advice :)
Semantics and markup discussions finished please do what you think best
I'm just confusing the issue get things in and we'll worry about this sort
of detail another time.
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7210#comment:39>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list