TYPO3 Core

Can you provide more detailed information? Wich extensions do you talk about?

I just checked it in the source (tslib_pibase - search for BEGIN:) and tested it - and it works here... I added config.disablePrefixComment = 1 and it worked.
I think this might be a TS problem, did you maybe write
page.config.disablePrefixComment? I don't know if it does work in this case.
Greets, Sebastian

have a look at the source code on this page:
http://www.brx.at/en/service/

you will find this snippet:

<div class="tx-srlanguagemenu-pi1">

<span class="act"><a href="en/service/" onfocus="blurLink(this)">EN</a></span>

 <a href="de/service/" onfocus="blurLink(this)">DE</a>

</div>

my config setup looks like this:

config {
simulateStaticDocuments = 0
baseURL = 1
tx_realurl_enable = 1
prefixLocalAnchors = 1

ATagParams = onFocus="blurLink(this)" 
  spamProtectEmailAddresses = 3
  spamProtectEmailAddresses_atSubst =<span class="accent"> AT </span>

titleTagFunction = user_pageTitle
  removeDefaultJS = external
  inlineStyle2TempFile = 1
  admPanel = 0
  notification_email_urlmode =
  content_from_pid_allowOutsideDomain = 1
  disablePrefixComment = 1
}

config.disablePrefixComment is ignored from other extension as well f.e. th_specialelements, jk_poll etc.

I quickly set up another example (tx_jphcodesnippets_pi) on http://www.brx.at/index.php?id=515 , you will find:

somehtmlhere

greets, b

I cannot tell you why it doesn't work in your installation, and without debugging your installation (which is not possible I guess?) I cannot solve this... Most likely, this is somewhere a configuration problem.
Is there any case where the comment is removed when you switch config.disablePrefixComment on?
Greets, Sebastian

no, there is no case. in two other installations it also does not function.... (3.8.0, php 4.3.9)

i tried to place disablePrefixComment = 1 on various places in the setup. i tried before/after PAGE, in a txt-file with INCLUDE_TYPOSCRIPT, config {disablePrefixComment = 1}, with no success.

is there any error in the typoscript object browser? the configuration option works flawlessly everywhere else I think.
greets, sebastian

no, no error in TSOB. I fugured out that disablePrefixComment will function f.e. with chc_forum, but not with f.e. with indexed_search, jk_poll...

I just checked again and noticed that this bug exists with TYPO3 3.8.0
However, in CVS it was already solved by Michael Stucki:

2005-07-02 Michael Stucki <michael@typo3.org> * config.disablePrefixComment was ignored by plugins

So this bug won't exist in TYPO3 4.0 anymore.
Greets, Sebastian