it is a bug the last-activity-time should be a number...<span class="data"><span class="last-activity-time">b13dce689732844e6590da37048f0eaf</span></span>
In the Tavern I noticed the gravatars not becoming opaque after a while:
Inspection of the html dom revealed this inside the <li> of balpha:
<span class="data">
<span class="last-activity-time">b13dce689732844e6590da37048f0eaf</span>
</span>
while for others that same html fragment shows:
<
@JonEricson That's certainly a nice addition, but I don't think it will catch everything. On the other hand, you're right that the phone number regex gives many false alerts.
@Undo @hichris123 @Manishearth What's your opinion on the above?
@JonEricson Andy has a pull request that has better phone number detection, we could use that instead. @Andy Your pull request cannot be merged now. Could you please rebase it?
@hichris123 Hm, that pull request I have doesn't detect that first one as a valid phone number
@ProgramFOX Done. Turns out the problem was the changed RegExs since February. I'm not sure how to trigger GitHub to say if it's ready to merge or not though. It still says it's not
This userscript is a revival of sorts for the old SE Editor Toolkit, which was abandoned some time ago.
It only really provides the autocorrect aspect for the foreseeable future, which I find to be quite useful.
It works by injecting a button in the edit window (it works inline for users with f...
In the Tavern I noticed the gravatars not becoming opaque after a while:
Inspection of the html dom revealed this inside the <li> of balpha:
<span class="data">
<span class="last-activity-time">b13dce689732844e6590da37048f0eaf</span>
</span>
while for others that same html fragment shows:
<
This userscript is a revival of sorts for the old SE Editor Toolkit, which was abandoned some time ago.
It only really provides the autocorrect aspect for the foreseeable future, which I find to be quite useful.
It works by injecting a button in the edit window (it works inline for users with f...