-
Notifications
You must be signed in to change notification settings - Fork 16
advanced html5 #30
Comments
By "advanced" do they mean "things in HTML5 that weren't in HTML4"? |
It would indeed be useful to get a more precise idea of what they meant cos’ there’s a lot of stuff you can put under “advanced HTML5” e.g. form inputs, |
Great questions! I have the contact information for the respondent that contributed this need and am happy to put whoever takes the lead on this ticket in touch with them to hash out more information about the needs. @JayPanoz it's the same person as asked about CSS if you'd like to try your hand at both of these? |
Yeah no problem I can try dealing with both. @dauwhe Do you want to be cc’ed? |
@JayPanoz - I can't seem to assign this to you mietkiewicz@gutenberg.technology submitted the initial question to the BISG Survey. Please feel free to reach out to him for more information. As you explore this topic - please keep this guiding structure in mind:
When you are proposing language/contributions to best practice, please consider and respond to the following questions:
|
@RachelComerford Are you sure this is the good email address? I’ve just seen a mailer–daemon in the spam folder (can’t even explain why it was put in there in the first place). And when trying re-sending it with their website’s url, mailer-daemon again. Did a super quick check on LinkedIn and it seems the person is not at the company anymore. |
Looks like he just left in March... Seth Puri can likely find us a new contact: Seth Puri spuri@gutenberg-technology.net I can reach out to him and ask, or you can. Up to you! |
Yeah I’ll take care of that, they’re also a French Company and one of their original co-founder happens to be a friend so don’t bother with it. |
I just left the group and will consequently be unable to keep working on this issue. But please contact me to pick up where I left off – sorry, DGPR in Europe so I can’t post email adresses publicly and in theory, I shouldn’t even pass them privately. |
(Request via BISG research)
The text was updated successfully, but these errors were encountered: