« first day (1362 days earlier)      last day (3341 days later) » 

8:52 AM
@Letharion can I have few minutes of your time?
 
@Mołot Sure :)
 
I have weirdest problem in days
I already posted it as a bugreport, but it's not the best report I did, I admit it
This "hide" comes from show / hide of collapsible fieldsets
but my tabs are not collapsible fieldsets
Ones rendered directly are not affected. Only ones added via AJAX are
And I have no idea how to bite it
started after last core upgrade
I admit, I feel dumb, don't know where to start to make a workaround :/
On the other hand, I don't know how to ask it as a question, either
I would vote to close as bugreport myself ;)
Wouldn't be the first time I voted close on my own question, but I refuse to ask it when I know it's not OK...
 
@Mołot lol.
Hmm, well, there's of course the immediate and ugly hack to post process the ajax call and remove the "Hide" ;)
Which is awful but the fastest solution that comes to mind.
 
Lol at closing own questions? Only did it for duplicates I believed my wording may be useful
 
@Mołot Ah, I see.
Yeah, it sounded funny to vote to close on own questions.
 
9:02 AM
@Letharion I would much prefer something a bit less ugly ;) because there is legitimate "Hide" in some instances
 
@Mołot Between what versions was the core upgrade? Is it feasible to do a git bisect?
 
Also, in the code returned from server there is no "Hide" added. It is added client-side
@Letharion I know from personal experience it was all right at 7.28, and no one reported this bug before 7.34
It is an old, well used piece of code I haven't any need to touch for a long time.
It is used by about a dozen people, daily, so I think it is safe to assume ot happened between 7.32 and 7.34
Might get unreported during 7.33
 
@Mołot So the number of js changes done between 7.32 and 7.34, I would expect to be rather small. Can you check the diff between those two tags, and identify the source of the problem that way?
 
Good point. Will try
 
@Mołot I tried a git diff 7.32..7.34, and it's interesting that there's changes to both ajax.inc and ajax.js. The changes look innocent enough at first glance to me, but try patching them out.
 
9:16 AM
@Letharion but only thing I see added is Command to add css
Will try, but if it will help, I'll be most surprised
 
 
5 hours later…
1:57 PM
@Mołot Any luck?
 
2:19 PM
@Letharion Kinda... I managed to crash one of my testing servers ;) but it seems that setting '#collapsible' => FALSE fixes it, and not setting it at all is now wrong thing to do
 
@Mołot Hmm, interesting. Any idea where the change comes from?
 
Sadly, no
And that really bothers me
It is interesting, but it is one of these situations where I'd love to be bored
@Letharion see drupal.stackexchange.com/questions/137834/… - was I too rough? :(
 
2:44 PM
@Mołot Doesn't look like it to me. :)
 
 
4 hours later…
7:05 PM
posted on November 24, 2014 by tvn

Several weeks ago, we issued an RFP for Drupal.org Content Strategy project. We got a number of great submissions, and the next couple of weeks the Drupal Association staff and the Drupal.org Content Working Group members spent reviewing proposals and interviewing potential vendors. Today we are happy to announce that we’ve selected a vendor for the content strategy project: Forum One, an ope

 

« first day (1362 days earlier)      last day (3341 days later) »