Loading Profile...
Please implement Textile in full!
There are so many things that I like about GoPlan but here's another thing I don't...
It seems that one can't insert IDs for in-page anchors using Textile syntax as one can in Basecamp. For me, this is invaluable as it allows one to create links within necessarily long posts.
For example, today I just created a post in a GoPlan project that gave a run down of a visual presentation I had made including visuals. At the end of the post was a section on conclusions and next steps. I wanted to be able to create some skip links at the top so that people could jump straight to those aspects. So I had some headings marked up for Textile such as...
h2(#next). Next steps
And a link above that along the lines of...
Skip to read up on "next steps":#next.
But then I find that GoPlan strips out the id set on the h2!
And the lack of a preview option is driving me nuts.
I'm sorry to say that I'm only using GoPlan right now because it's already up and running on a project. Unless my many concerns can be addressed some time soon, I'll be going back to Basecamp.
It seems that one can't insert IDs for in-page anchors using Textile syntax as one can in Basecamp. For me, this is invaluable as it allows one to create links within necessarily long posts.
For example, today I just created a post in a GoPlan project that gave a run down of a visual presentation I had made including visuals. At the end of the post was a section on conclusions and next steps. I wanted to be able to create some skip links at the top so that people could jump straight to those aspects. So I had some headings marked up for Textile such as...
h2(#next). Next steps
And a link above that along the lines of...
Skip to read up on "next steps":#next.
But then I find that GoPlan strips out the id set on the h2!
And the lack of a preview option is driving me nuts.
I'm sorry to say that I'm only using GoPlan right now because it's already up and running on a project. Unless my many concerns can be addressed some time soon, I'll be going back to Basecamp.
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hey Jonathan,
You are absolutely right. For security measures, we were removing the id attributes from headlines - we didn't consider people who might make use of the anchor tag syntax from textile. Meaning, we do implement textile in full - we were just stripping a few details off that made using anchors impossible.
Thanks for pointing it out - this has just been fixed and should go live first thing tomorrow (we update our code in the morning in order not to affect as much people) - with the other typography stuff we talked about earlier.
As for previewing: it is definitely a more complex change, but one we're working on ;-)
I’m confident
The company says
this answers the question
-
Inappropriate?Thanks, Fred. I really appreciate your responsiveness. Just out of interest, what are/were the security implications of id attributes in HTML?
I’m happy
2 Comments Add a comment
This answers the question
-
Haha, well, there's no direct implication. We were just removing any attributes that could be used by malicious javascript code (and removing the javascript too). I guess one could say we were over zealous with our security tightness and decided to remove everything we thought people wouldn't use :-) -
Thanks for your candour!
EMPLOYEE
