vanilla-css
vanilla-css copied to clipboard
aethant
Call my boss
Tell him I won't be in tomorrow because I'm too busy working on this vanilla CSS project. Tell him it's going to change the world as he knows it.
No phone number, not enough information to complete this issue. :-1:
Will update if I miss the bus, otherwise I'll close the issue and file as won't fix
I vote to leave this open for a somewhat indefinite period of time. There's a slightly high probability... >20% that I might also need to call my boss for this issue as well.
Right, update. No need to call my boss, I think I will make the morning meeting.
However... I at with @jxm262 on this one. Could be a recurring issue until someone fixes the root cause of the problem. Any suggestions welcome.
This could be solved by adding IoT into the mix. This should add almost no additional technical debt to the project.
My guess is he didn't miss his bus, so he should have closed it. @neutraltone :question:
I wonder if we should leave this open and add this to the next VanillaCSS Foundation meeting?
Using my power as project collaborator to veto this close and reopen the ticket. This issue is still not resolved and can be reproduced by visiting my desk at work. Confirmed I am still here and not at home.
Keeping open until next week at least
This difficult to reproduce. Can we label as intermittent? I'm unable to visit my desk at all times. There seems to be a pattern. Needs further investigation.
On Fri, 4 Dec 2015 22:33 Justin Maat [email protected] wrote:
Reopened #13 https://github.com/aethant/vanilla-css/issues/13.
— Reply to this email directly or view it on GitHub https://github.com/aethant/vanilla-css/issues/13#event-482686771.
@hectorpalmatellez, @jxm262, @Seikho, @aethant:
Might have to call and issue #13 on tomorrow's activities. Will keep you all posted.
@neutraltone that's perfectly fine. Just keep in mind this issue is still relevant to many of us working on this app. Feel free to work on #13 tomorrow, but please leave the ticket open. I know I haven't been too active here recently, but the reason for my recent absence directly relates to this specific issue (overworked, can't do this ticket myself yet).
Please let us know if you make any progress on this.
OK I might have to reinstate this. I fell into a boozer this evening and subsequently ended up several pitchers deep. It's OK I managed to get home but at which point a bottle Casillero del Diablo (CC:@hectorpalmatellez) forced itself upon me. There was nothing I could do. It made me watch The Sixth Sense.
I think I might be OK, I've managed to convince Diablo to go back into the cupboard but who know's when he'll surface again. Please keep this issue in mind.
Help a brother out.
Siempre debes respetar al diablo y su casillero, @neutraltone.
Your boss will understand, I'm sure.
Sorry to resurrect but I've had to many @Hectorpalmatellez's, I think it might be unmerable...
Casillero del Diablo
👎 desperate times, off-licence favourite though. Usually end up throwing an exception in the toilet.
This seems to be a recurring case of rectal glaucoma. Not a code based issue.
Did anyone call my boss? I don't work for him anymore but feel free to phone and call him a cheapskate.
Him and his team of clairvoyants already knew you were going to post that comment, @neutraltone. Notifying him will be unnecessary.
Recent activities in the application have cause issue to resurface. Reopening so we can get to the bottom of this.
@aethant can you call my boss?
I don't even know where you work, mate. Just have another bitter and lean into it. I'm sure it'll be fine.
@aethant can you call my boss?
Does the css api support this?
Theoretically, yes.
.sobriety {
display: none;
}
I feel like the CSS api is too powerful. Is the world ready for something like this? Have we gone too far?
Hi has anyone called @neutraltone's boss yet? We're adding this to our codebase and need this resolved
