Wedge
Public area => Bug reports => The Pub => Archived fixes => Topic started by: oOo--STAR--oOo on April 21st, 2012, 10:24 PM
-
Hey,
I just replied to nao's statement about baidu bots, and when I initially submitted it, it didn't display @nao
When I refreshed it then displayed the @nao, but didn't display it when I initially posted it.
I am using google chrome.
-
That's not a bug, that's exactly as designed.
-
That's not a bug, that's exactly as designed.
Thought it was a bug lol.
-
Hence the 'refresh to interact' too ;)
-
I can probably make it show everything as needed though. This hack was a quick fix when I developed the feature. I just don't remember why I failed to make it work even though it sends the thought back via Ajax...
-
I can probably make it show everything as needed though. This hack was a quick fix when I developed the feature. I just don't remember why I failed to make it work even though it sends the thought back via Ajax...
The response is probably different than the display all. As in you not included the @ in the response.
-
Let's be clear. The thought system is not 100% finished. It still has a few bugs (try to post a new thought from the sidebar, then try to 'Modify' it immediately without reloading the page... It won't show you the current thought, even though there's one.)
I just don't think it's a huge priority right now. Priorities should basically be whatever will be hard to modify *after* we go live...
For instance, the work I'm doing now on the language files... It's something that's going to be annoying to translators if it's done *after* the first public release.
-
Can this be moved?
-
It's not quite perfect yet.
The dynamically-added item doesn't have the link image back to the profile area, and for some reason the dynamically added name does not have the user link colouring, e.g. if I reply to a thought, the @ name in the reply does not take on the colouring for consultants or admins.
-
Yup, I noticed that...
Actually, I miss the days when the @ names were all shown in gray... It made the overall look a bit less confusing. (But less logical as well.)
But in the end, all I can say is that it shouldn't be behaving that way. AFAIK the returned Ajax thought goes through output buffers so it should be transforming any member links to use their group color...
-
That's a fixed issue, btw...