aroc / side-comments Goto Github PK

The current main theme styles don't account for styling that the site SideComments is being integrated on have. For example, some sites have box shadows on all inputs and this effects the SideComments comment box.

Add in properties for those styles to ensure SideComments looks as expected.

To fully comply with WordPress comments API and support comment author website url or trackbacks, a link should wrap the author name with the specified url.

Receiving the following syntax error when trying to run - this is seen on the test site as well: https://tonicdev.com/npm/democracyos-side-comments

(function (exports, require, module, __filename, __dirname) { <div class="side-comment <%= sectionClasses %>">
                                                              ^

SyntaxError: Unexpected token <

Currently comments allow to add arbitrary HTML tags including <script>

Would love to use only this on my blog, doing away entirely with Wordpress comments. Is there a way to also therefore include comments at the "end of a post" instead of just the side? How will it become obvious to a user on touch devices, where there's no mouseover to suggest the presence of a commentable icon?Thank you!

Right now the placeholder text disappears even on focus. It would be awesome to still show the placeholder until the first character is entered into the form.

How would i save this to local storage .

Hi @aroc ,

Just fork this cool library. And I am struggling building it with gulp. The current gulpfile even pointing to the wrong paths.scripts. Can you explain the way you're building / releasing it? Thanks.

To give ability for unlogged users to leave comments, the name label should be editable (input field) if the user is unknown.

If you show the comments for a section without any comments yet, it shows the comment form immediately. However, the comment form is displayed much wider than it is and then snaps to a smaller size afterwards, causing a jump in the DOM.

Hello.
I see that the last update is from 1 year .
The project is DEAD?

e.g. I can't get the require function to work and just want to include this as html / css on my page.

How do I do that and still get this to work?

Thanks

Medium and many other commenting platforms offer this right now.

You don't load fontawesome on demo website.

@aroc It'll be good to have feature to edit the already present comments. Provide an event to handle it just like Add and Delete.

Hi there,

Is it possible to not use Jquery, cause there is a few such a good js libs which do DOM manipulation much better, faster and optimized then Jquery ?

Peace,

I've got an issue with side-comments. It's too dope.

Too dope to handle.

Could you add bower support?

If using jQuery no-conflict or with another library, we have conflicts using the $ symbol.

ex: $(el) should be jQuery(el)

Hi --

I stumbled across the Medium site and liked their commenting system. Then I stumbled on your project.

How, or does, your project support comments on content as it goes through revisions? If I have 3 paragraphs and publish my article, and each paragraph gets a comment -- what happens when a new paragraph is added between existing paragraphs, or added to the end of the document?

I see no explanation on how a website should generate a meaningful section-id which could successfully track comments through an articles editorial history.

would it be as simple as a stylesheet and a flag that sets the comment icons as draggable?

Hi there,

In order to be able to fully integrate this within WordPress (or any other platform which provides native comment forms) it'd be great to have the ability to say "Hey, this is my comment form textarea. It has an ID of #comment-form (for example). Use that."

This way, I can use the native WP Comment Form (and all of the hooks that it provides) so any plugins which tie into that form should just work.

What do you think?

The comment form doesn't work well on mobile. Many times the comment text doesn't even show in the comment box.

@aroc buddy, you should probably set lodash as a local variable in comment.js :)