Opened 18 years ago
Closed 13 years ago
#185 closed New Feature (wontfix)
.Value property vs .Text property
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | Server : ASP.Net | Version: | |
| Keywords: | SF | Cc: |
Description
I noticed the FCKeditorV2 dll uses the .Value property to represent the text in the textbox. This makes integrating the editor into existing applications difficult because I have to change all instances of myTextBox.Text to myTextBox.Value.
As far as the code-behind, it really should operate like a standard textbox.
Moved from SF:
http://sourceforge.net/tracker/index.php?func=detail&aid=1592309&group_id=75348&atid=543653
Change History (5)
comment:1 Changed 18 years ago by
| Reporter: | changed from Frederico Caldeira Knabben to anonymous |
|---|
comment:2 Changed 18 years ago by
| Type: | Bug → New Feature |
|---|
comment:3 Changed 17 years ago by
| Owner: | Frederico Caldeira Knabben deleted |
|---|
comment:4 Changed 16 years ago by
| Keywords: | Confirmed added |
|---|
comment:5 Changed 13 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | confirmed → closed |
In new version CKEditora.NET property .Text is used.
Note: See
TracTickets for help on using
tickets.
I agree that the .Text property wold be a good thing. We have used .Value because this is the name used in all other server side integrations. I believe we should make .Text an alias of .Value.